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 Massimiliano Masi <ma...@math.unifi.it> on 2007/10/05 10:07:15 UTC
Axis2 and rampart design question
Hi all,
I am trying to setup a webservice that acts as WS-Trust STS with rampart.
I've a design question.
Clients sends the authentication claim in the wsse:Security element in the
header (claims such as Username/Password, SAML Tokens, Kerberos and
X.509 binary secrets). Based on the identity carried in this wsse:Security,
the STS decide to issue or not the security token (that is my own
implementation
of SAML2).
Now I'm thinking: the wsse:Security element is detached by a module (that I
will write I think, to get all my claims processed). But, detaching the
header, I don't know anymore the identity of the user! So, I thought to
put in the header of the SOAP message something like
<identity>userIdentity</identity>
so the STS implementation can have the information on the identity of the
user (and can decide to issue a token).
Have you other ideas? Does it looks good for you? Have you any pattern?
I'll appreciate your hints!
Thank you!
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and rampart design question
Posted by Massimiliano Masi <ma...@math.unifi.it>.
Hi Dimuthu,
Quoting Dimuthu <mu...@apache.org>:
> If you want to configure claims you can use the callback mechanism as in
> this test case[1].
Thank for your answer. I took as example the STSClient test from wsas [1]
and the security policy for the server and the client. I also created the
keystore as described here [2]. I put in my services.xml the following:
<module ref="rampart" />
<operation name="IssueToken" mep="http://www.w3.org/2006/01/wsdl/in-out">
<messageReceiver class="org.apache.rahas.STSMessageReceiver"/>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Renew</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Cancel</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/Cancel</actionMapping>
<actionMapping>http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Validate</actionMapping>
<parameter name="token-dispatcher-configuration">
<token-dispatcher-configuration>
<issuer class="com.test.TokenIssuer" default="true">
<configuration type="parameter">saml2-issuer-config</configuration>
<tokenType>urn:oasis:names:tc:SAML:2.0:assertion</tokenType>
</issuer>
</token-dispatcher-configuration>
</parameter>
</operation>
But I got this error:
[java] Caused by: org.apache.ws.security.WSSecurityException: An
unsupported signature or encryption algorithm was used (unsupported
key transport encryption algorithm: No such algorithm:
http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p)
Have you any idea? And, there is an example of a STS service?
Thank you,
[1] WSAS Example:
http://wso2.org/repos/wso2/trunk/wsas/java/modules/samples/sts-sample/src/org/wso2/wsas/sample/sts/client/Client.java
[2] Keystore http://wso2.org/library/174
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 and rampart design question
Posted by Dimuthu <mu...@apache.org>.
Hi,
If you want to configure claims you can use the callback mechanism as in
this test case[1].
If you want to obtain Username/passowrd then you can do it as specified
here[2]. You can look at this class for more different types of
results[3]
Thank you,
Dimuthu
[1]https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-integration/src/test/java/org/apache/rahas/SAMLDataProvider.java
[2]http://wso2.org/library/169
[3]https://svn.apache.org/repos/asf/webservices/wss4j/trunk/src/org/apache/ws/security/WSSecurityEngineResult.java
On Fri, 2007-10-05 at 10:07 +0200, Massimiliano Masi wrote:
> Hi all,
>
> I am trying to setup a webservice that acts as WS-Trust STS with rampart.
> I've a design question.
>
> Clients sends the authentication claim in the wsse:Security element in the
> header (claims such as Username/Password, SAML Tokens, Kerberos and
> X.509 binary secrets). Based on the identity carried in this wsse:Security,
> the STS decide to issue or not the security token (that is my own
> implementation
> of SAML2).
>
> Now I'm thinking: the wsse:Security element is detached by a module (that I
> will write I think, to get all my claims processed). But, detaching the
> header, I don't know anymore the identity of the user! So, I thought to
> put in the header of the SOAP message something like
> <identity>userIdentity</identity>
> so the STS implementation can have the information on the identity of the
> user (and can decide to issue a token).
>
> Have you other ideas? Does it looks good for you? Have you any pattern?
> I'll appreciate your hints!
>
>
> Thank you!
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
--
http://wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org