axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruchith Fernando" <>
Subject Re: AXIS2: Rampart: Support for IssuedToken
Date Wed, 01 Aug 2007 05:15:38 GMT
Hi Nagi,

Yes ... Rampart does support protecting messages with IssuedTokens.
But this is not available with the parameter based configuration.
Suport for issued tokens is available with the new policy based
configuration which uses WS-SecurityPolicy.

Right now we do not automatically obtain the token from the issuer and
we expect the client developer to provide the issued token which we
can use. One can use org.apache.rahas.client.STSClient to obtain a
token from an STS (SecurityTokenService). This token should be made
available to rampart in the options object. Please see this sample
client [1] from WSO2 WSAS[2]. You can try out this sample in the
latest 2.0 release of WSAS [3]


p.s. Please subscribe and post rampart related questions to the list

On 8/1/07, Par Nagi <> wrote:
> Hi,
> Does Axis2/Rampart support services that expect a SAML (or other
> issued token) at present? I.e., can I write a service.xml where I
> specify the InflowSecurity parameter as follows?
>   <parameter name="InflowSecurity">
>     <action>
>      <items>IssuedToken</items>
>     </action>
>   </parameter>
> I get an AxisFault - WSDoAllSender: Unknown action definedIssuedToken.
> Clearly the items being set to IssuedToken is not right in the above
> service.xml - what is the correct value for the items tag to notify
> Axis that the service expects an issued token such as SAML?
> Thanks for any info
> - Nagi
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message