You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Francesco Stampacchia <st...@gmail.com> on 2009/09/28 13:00:47 UTC
WS-Trust with Rampart
It is possible to exploit WS-Trust operations with the new Rampart release?!
If so, could you point me to some references or best practices?!
Thanks
--
Francesco Stampacchia
Re: WS-Trust with Rampart
Posted by Francesco Stampacchia <st...@gmail.com>.
Hello Nanadana,
In the previous mails you stated that the third step:
3.) WS - B ---- SAML2 (signed by STS - A) / validate --------> STS B
Could be worked out with little efforts, does it mean that Rampart does not
provide broker trust between STS?
If so or otherwise, how can I work out broker trust? Is there any
best-practices, code or how-to that you can point me to?!
Thanks.
2009/9/29 Francesco Stampacchia <st...@gmail.com>
> Yes this is my scenario. Are there any guides that can point me in the
> right direction in order to work out this environment?!
>
> But in order to validate my assertion only if the sender is trusted, do I
> have to exchange Trust in between STS A and STS B?!
>
> Thanks
>
> 2009/9/29 Nandana Mihindukulasooriya <na...@gmail.com>
>
> Sorry, I was busy with some lectures yesterday. You are talking about
>> the following scenario, right ? This is possible with Rampart, but
>> third step is not done by Rampart by default. Normally Rampart tries
>> to validate the token by it self, but this can be done with little
>> effort.
>>
>> thanks,
>> Nandana
>>
>> 1.) WS - A ---- credentials
>> ---------------------------> STS - A
>> <---- SAML2 (signed by STS - A) ----------------
>>
>> 2.) WS - A ------------- SAML2 (signed by STS - A) ----------> WS - B
>>
>> 3.) WS - B ---- SAML2 (signed by STS - A) / validate --------> STS B
>>
>> 4.) WS - A <----------------- response ------------------------------ WS -
>> B
>>
>> On Tue, Sep 29, 2009 at 10:30 AM, Francesco Stampacchia
>> <st...@gmail.com> wrote:
>> > Hello Nandana,
>> > Have you got some news about the question I asked you yesterday?
>> >
>> > Thanks.
>> >
>> > 2009/9/28 Francesco Stampacchia <st...@gmail.com>
>> >>
>> >> I've got a WSC on domain A that has to access a WS on domain B.
>> >> WSC would present its credentials to its local STS and so obtains a
>> SAML2
>> >> Assertion.
>> >> Then the newly generated assertion is sent to the WS.
>> >> The WS will present the received assertion to its STS in order to
>> validate
>> >> it. Validation will be succsessful only if both STS are federated.
>> >>
>> >> Thanks
>> >>
>> >> 2009/9/28 Nandana Mihindukulasooriya <na...@gmail.com>
>> >>>
>> >>> Yes, it is possible to use Rampart for trust operation and by default
>> >>> Rampart comes with a token issuer, renewer, validator and canceller
>> >>> for SAML tokens. What exactly is your scenario ?
>> >>>
>> >>> thanks,
>> >>> Nandana
>> >>>
>> >>>
>> >>> ---------- Forwarded message ----------
>> >>> From: Francesco Stampacchia <st...@gmail.com>
>> >>> Date: Mon, Sep 28, 2009 at 1:00 PM
>> >>> Subject: WS-Trust with Rampart
>> >>> To: axis-user@ws.apache.org
>> >>>
>> >>>
>> >>> It is possible to exploit WS-Trust operations with the new Rampart
>> >>> release?!
>> >>> If so, could you point me to some references or best practices?!
>> >>>
>> >>> Thanks
>> >>>
>> >>> --
>> >>> Francesco Stampacchia
>> >>
>> >>
>> >>
>> >> --
>> >> Francesco Stampacchia
>> >
>> >
>> >
>> > --
>> > Francesco Stampacchia
>> >
>>
>
>
>
> --
> Francesco Stampacchia
>
--
Francesco Stampacchia
Re: WS-Trust with Rampart
Posted by Francesco Stampacchia <st...@gmail.com>.
Yes this is my scenario. Are there any guides that can point me in the right
direction in order to work out this environment?!
But in order to validate my assertion only if the sender is trusted, do I
have to exchange Trust in between STS A and STS B?!
Thanks
2009/9/29 Nandana Mihindukulasooriya <na...@gmail.com>
> Sorry, I was busy with some lectures yesterday. You are talking about
> the following scenario, right ? This is possible with Rampart, but
> third step is not done by Rampart by default. Normally Rampart tries
> to validate the token by it self, but this can be done with little
> effort.
>
> thanks,
> Nandana
>
> 1.) WS - A ---- credentials
> ---------------------------> STS - A
> <---- SAML2 (signed by STS - A) ----------------
>
> 2.) WS - A ------------- SAML2 (signed by STS - A) ----------> WS - B
>
> 3.) WS - B ---- SAML2 (signed by STS - A) / validate --------> STS B
>
> 4.) WS - A <----------------- response ------------------------------ WS -
> B
>
> On Tue, Sep 29, 2009 at 10:30 AM, Francesco Stampacchia
> <st...@gmail.com> wrote:
> > Hello Nandana,
> > Have you got some news about the question I asked you yesterday?
> >
> > Thanks.
> >
> > 2009/9/28 Francesco Stampacchia <st...@gmail.com>
> >>
> >> I've got a WSC on domain A that has to access a WS on domain B.
> >> WSC would present its credentials to its local STS and so obtains a
> SAML2
> >> Assertion.
> >> Then the newly generated assertion is sent to the WS.
> >> The WS will present the received assertion to its STS in order to
> validate
> >> it. Validation will be succsessful only if both STS are federated.
> >>
> >> Thanks
> >>
> >> 2009/9/28 Nandana Mihindukulasooriya <na...@gmail.com>
> >>>
> >>> Yes, it is possible to use Rampart for trust operation and by default
> >>> Rampart comes with a token issuer, renewer, validator and canceller
> >>> for SAML tokens. What exactly is your scenario ?
> >>>
> >>> thanks,
> >>> Nandana
> >>>
> >>>
> >>> ---------- Forwarded message ----------
> >>> From: Francesco Stampacchia <st...@gmail.com>
> >>> Date: Mon, Sep 28, 2009 at 1:00 PM
> >>> Subject: WS-Trust with Rampart
> >>> To: axis-user@ws.apache.org
> >>>
> >>>
> >>> It is possible to exploit WS-Trust operations with the new Rampart
> >>> release?!
> >>> If so, could you point me to some references or best practices?!
> >>>
> >>> Thanks
> >>>
> >>> --
> >>> Francesco Stampacchia
> >>
> >>
> >>
> >> --
> >> Francesco Stampacchia
> >
> >
> >
> > --
> > Francesco Stampacchia
> >
>
--
Francesco Stampacchia
Re: WS-Trust with Rampart
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Sorry, I was busy with some lectures yesterday. You are talking about
the following scenario, right ? This is possible with Rampart, but
third step is not done by Rampart by default. Normally Rampart tries
to validate the token by it self, but this can be done with little
effort.
thanks,
Nandana
1.) WS - A ---- credentials
---------------------------> STS - A
<---- SAML2 (signed by STS - A) ----------------
2.) WS - A ------------- SAML2 (signed by STS - A) ----------> WS - B
3.) WS - B ---- SAML2 (signed by STS - A) / validate --------> STS B
4.) WS - A <----------------- response ------------------------------ WS - B
On Tue, Sep 29, 2009 at 10:30 AM, Francesco Stampacchia
<st...@gmail.com> wrote:
> Hello Nandana,
> Have you got some news about the question I asked you yesterday?
>
> Thanks.
>
> 2009/9/28 Francesco Stampacchia <st...@gmail.com>
>>
>> I've got a WSC on domain A that has to access a WS on domain B.
>> WSC would present its credentials to its local STS and so obtains a SAML2
>> Assertion.
>> Then the newly generated assertion is sent to the WS.
>> The WS will present the received assertion to its STS in order to validate
>> it. Validation will be succsessful only if both STS are federated.
>>
>> Thanks
>>
>> 2009/9/28 Nandana Mihindukulasooriya <na...@gmail.com>
>>>
>>> Yes, it is possible to use Rampart for trust operation and by default
>>> Rampart comes with a token issuer, renewer, validator and canceller
>>> for SAML tokens. What exactly is your scenario ?
>>>
>>> thanks,
>>> Nandana
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Francesco Stampacchia <st...@gmail.com>
>>> Date: Mon, Sep 28, 2009 at 1:00 PM
>>> Subject: WS-Trust with Rampart
>>> To: axis-user@ws.apache.org
>>>
>>>
>>> It is possible to exploit WS-Trust operations with the new Rampart
>>> release?!
>>> If so, could you point me to some references or best practices?!
>>>
>>> Thanks
>>>
>>> --
>>> Francesco Stampacchia
>>
>>
>>
>> --
>> Francesco Stampacchia
>
>
>
> --
> Francesco Stampacchia
>
Re: WebService issue - "Too many files open"
Posted by E Shanaka Jayasundera <sh...@aeturnum.com>.
I wanted to monitor WSDL and we have configure NagiOs to check WSDL's
status, so thats why its request WSDL and crashes with "Too many files
open" ioexception.
Thanks,
Shanaka
On 09/29/2009 07:28 PM, Amila Suriarachchi wrote:
> On Tue, Sep 29, 2009 at 2:54 PM, E Shanaka Jayasundera<shanaka@aeturnum.com
>> wrote:
>
>> Hi,
>>
>> If the webservice is running for a long time, it crashes with "Too many
>> files open" ioexception. This happens because our wsdl context is loaded
>> many times
>> Can anyone please help me to solve this issue.
>>
>> I tried disabling hot deployment as well but still I am getting this issue.
>> ( I disable the hot deployment in axis2.xml file)
>>
>
> Are you doing invocations to other web services using a stub or service
> client?
>
> in that case create only one configuration context for all those
> invocations.
>
> thanks,
> Amila.
>
>>
>> Thanks in advance.
>> Shanaka
>>
>>
>
>
Re: WebService issue - "Too many files open"
Posted by Amila Suriarachchi <am...@gmail.com>.
On Tue, Sep 29, 2009 at 2:54 PM, E Shanaka Jayasundera <shanaka@aeturnum.com
> wrote:
> Hi,
>
> If the webservice is running for a long time, it crashes with "Too many
> files open" ioexception. This happens because our wsdl context is loaded
> many times
> Can anyone please help me to solve this issue.
>
> I tried disabling hot deployment as well but still I am getting this issue.
> ( I disable the hot deployment in axis2.xml file)
>
Are you doing invocations to other web services using a stub or service
client?
in that case create only one configuration context for all those
invocations.
thanks,
Amila.
>
> Thanks in advance.
> Shanaka
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
WebService issue - "Too many files open"
Posted by E Shanaka Jayasundera <sh...@aeturnum.com>.
Hi,
If the webservice is running for a long time, it crashes with "Too many
files open" ioexception. This happens because our wsdl context is loaded
many times
Can anyone please help me to solve this issue.
I tried disabling hot deployment as well but still I am getting this
issue. ( I disable the hot deployment in axis2.xml file)
Thanks in advance.
Shanaka
Re: WS-Trust with Rampart
Posted by Francesco Stampacchia <st...@gmail.com>.
Hello Nandana,
Have you got some news about the question I asked you yesterday?
Thanks.
2009/9/28 Francesco Stampacchia <st...@gmail.com>
> I've got a WSC on domain A that has to access a WS on domain B.
> WSC would present its credentials to its local STS and so obtains a SAML2
> Assertion.
> Then the newly generated assertion is sent to the WS.
> The WS will present the received assertion to its STS in order to validate
> it. Validation will be succsessful only if both STS are federated.
>
> Thanks
>
> 2009/9/28 Nandana Mihindukulasooriya <na...@gmail.com>
>
> Yes, it is possible to use Rampart for trust operation and by default
>> Rampart comes with a token issuer, renewer, validator and canceller
>> for SAML tokens. What exactly is your scenario ?
>>
>> thanks,
>> Nandana
>>
>>
>> ---------- Forwarded message ----------
>> From: Francesco Stampacchia <st...@gmail.com>
>> Date: Mon, Sep 28, 2009 at 1:00 PM
>> Subject: WS-Trust with Rampart
>> To: axis-user@ws.apache.org
>>
>>
>> It is possible to exploit WS-Trust operations with the new Rampart
>> release?!
>> If so, could you point me to some references or best practices?!
>>
>> Thanks
>>
>> --
>> Francesco Stampacchia
>>
>
>
>
> --
> Francesco Stampacchia
>
--
Francesco Stampacchia
Re: WS-Trust with Rampart
Posted by Francesco Stampacchia <st...@gmail.com>.
I've got a WSC on domain A that has to access a WS on domain B.
WSC would present its credentials to its local STS and so obtains a SAML2
Assertion.
Then the newly generated assertion is sent to the WS.
The WS will present the received assertion to its STS in order to validate
it. Validation will be succsessful only if both STS are federated.
Thanks
2009/9/28 Nandana Mihindukulasooriya <na...@gmail.com>
> Yes, it is possible to use Rampart for trust operation and by default
> Rampart comes with a token issuer, renewer, validator and canceller
> for SAML tokens. What exactly is your scenario ?
>
> thanks,
> Nandana
>
>
> ---------- Forwarded message ----------
> From: Francesco Stampacchia <st...@gmail.com>
> Date: Mon, Sep 28, 2009 at 1:00 PM
> Subject: WS-Trust with Rampart
> To: axis-user@ws.apache.org
>
>
> It is possible to exploit WS-Trust operations with the new Rampart
> release?!
> If so, could you point me to some references or best practices?!
>
> Thanks
>
> --
> Francesco Stampacchia
>
--
Francesco Stampacchia
Re: WS-Trust with Rampart
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Yes, it is possible to use Rampart for trust operation and by default
Rampart comes with a token issuer, renewer, validator and canceller
for SAML tokens. What exactly is your scenario ?
thanks,
Nandana
---------- Forwarded message ----------
From: Francesco Stampacchia <st...@gmail.com>
Date: Mon, Sep 28, 2009 at 1:00 PM
Subject: WS-Trust with Rampart
To: axis-user@ws.apache.org
It is possible to exploit WS-Trust operations with the new Rampart release?!
If so, could you point me to some references or best practices?!
Thanks
--
Francesco Stampacchia