Axis Secure Conversation Handlers seems not to work properly
------------------------------------------------------------
Key: WSS-115
URL: https://issues.apache.org/jira/browse/WSS-115
Project: WSS4J
Issue Type: Bug
Environment: axis .5, wss4j 1.5.1
Reporter: Davide Gesino
Assignee: Ruchith Udayanga Fernando
I have a problem using the wss4j Axis Secure Conversation handlers.
I guess it is a bug.
org.apache.ws.sandbox.axis.security.conversation.ConversationClientHandler
org.apache.ws.sandbox.axis.security.conversation.ConversationServerHandler
Here's how I have configured the client side:
<deployment xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
<transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>
<globalConfiguration>
<requestFlow>
<handler
type="java:org.apache.ws.sandbox.axis.security.conversation.ConversationClientHandler"
>
<!-- STSRequestToken=3, InteropHandshake=4, DirectGenerated=1,
STSGenerated=2-->
<parameter name="sctEstablishmentMtd" value="DirectGenerated"/>
<parameter name="serverPropFile" value="client_security.properties"/>
<parameter name="serverAlias" value="myAlias"/>
<parameter name="keyFrequency" value="1"/>
</handler>
<handler type="java:org.apache.axis.handlers.LogHandler">
</handler>
</requestFlow>
</globalConfiguration>
</deployment>
I use the Direct Generated method to create the security context token.
Here's the SOAP message passing on the wire.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Header>
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
<wsse:BinarySecurityToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary";
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";
wsu:Id="EncCertId--39465">MIIBlTCB/wIERsmXRjANBgkqhkiG9w0BAQQFADASMRAwDgYDVQQDEwdteUFsaWFzMB4XDTA3MDgyMDEzMjk0MloXDTA3MTExODEzMjk0MlowEjEQMA4GA1UEAxMHbXlBbGlhczCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2wZL6NUEuhZ6iJkyJZXMlgpW3rOBNOiS1cmu7VTuNlEjaH07yOaCOR6riWXIH05WLhqo8XcFerbKckOELLmO3n8lf25fJOtbXTe/UvRVMzWgK9ibzLgawHUw8Efr6u53NPg8iL+zRP9emDLmiU1qAt9kfq4I6t7PtxUlJfFVN60CAwEAATANBgkqhkiG9w0BAQQFAAOBgQCIpV9bjjriAZ9WJOA5zzdaJ4keE7KRjATUOeEDKXzBkvmUNjTlfOseAcX9HKZqdM+M7TjHKWirKeZ1Ciog1RU1zpMoywMDqPR1ykba84nzpK4z1Wre6nmQ3emwHVuFu4YGzHULE3mBGpRu6eWI7BkfANVy3jvAS6N0t7F5KyTC6A==</wsse:BinarySecurityToken>
<wst:RequestSecurityTokenResponse> <!-
BEWAAAAAAAAAAAAAAAARE -->
<wst:RequestedSecurityToken
xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
<wsc:SecurityContextToken
xmlns:wsc="http://schemas.xmlsoap.org/ws/2005/02/sc";>
<wsc:Identifier>gwfZ+mYC+1KZt54aMJU1qTKS1VyGnTU9nH6T9WyG3w4=</wsc:Identifier>
</wsc:SecurityContextToken>
</wst:RequestedSecurityToken>
<wst:RequestedProofToken
xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust";>
<xenc:EncryptedKey>
<xenc:EncryptionMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5";>
</xenc:EncryptionMethod>
<ds:KeyInfo
xmlns:ds="http://www.w3.org/2000/09/xmldsig#";>
<wsse:SecurityTokenReference>
<wsse:Reference
URI="#EncCertId--39465"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3";>
</wsse:Reference>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>gv4cHh4Nij/8WZgKMJ51wwRzGRCAS6DB9wKjaYxOvoQY0bk8zLE0pYVEpGJ3YOD0yxydXVrNpn90mlVq5xaL0QKvZ/vu4xaYZa2R9VD88OgzutI4kWQzqczcWFH8ga8dxAjTGCo2KmXP+73wRYWxr8rWYGXzSivmkJ1kfbJTN0I=</xenc:CipherValue>
</xenc:CipherData>
<xenc:ReferenceList>
<xenc:DataReference
URI="#EncDataId-31098843">
</xenc:DataReference>
</xenc:ReferenceList>
</xenc:EncryptedKey>
</wst:RequestedProofToken>
</wst:RequestSecurityTokenResponse>
</wsse:Security>
</soapenv:Header>
<soapenv:Body>
<xenc:EncryptedData Id="EncDataId-31098843"
Type="http://www.w3.org/2001/04/xmlenc#Content";>
<xenc:EncryptionMethod
Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc";>
</xenc:EncryptionMethod>
<xenc:CipherData>
<xenc:CipherValue>ATKJdvdbMkJ9uxMAfj6wcS4FTkuM0i88a5+ajiu88dBUz4vUDsBbTWELY8mzCcLw92ROQLxHXgOy
LInRfCUBvuvLxsPllXsEhjfOPEJ2lJrmkdJNBS9SV4eusg/nRpKm/WlLOlv/VnZW9qn35KMzssRY
4+YBbdhZynYb2c7xTzzP0b7TugXKWI8hTKe+Zx1UCOqThQQrnLn+VhrVkzMfWkD1vYNsMkh77UKk
vugt6NCPBwGUlgvc1p987cLI/MNnn/DGI/sivTd6MKq59mSr6vXvrTJY2EhfE3JDgDCHP2T+dL1G
pbDQ+9J/5TClitYUiny+uAYiiILTbVOcfOqBTZWlz+YCk5MV7QbCqnltar9fomlS7+RWtYWYJKJ/
Mmj8rm8Z4o3WD1HPxS+IJWBXsasGTJqGkBHzJOywYwth9KU=</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</soapenv:Body>
</soapenv:Envelope>
On the server side I get an exception because the
<wst:RequestSecurityTokenResponse> does not have the namespace bound (I have
marked it on the text).
There's something wrong in the way i configure the handlers or is it a bug?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
