With SecureConv tokens, URI reference processing can strip off first char of
ID....
-----------------------------------------------------------------------------------
Key: WSS-162
URL: https://issues.apache.org/jira/browse/WSS-162
Project: WSS4J
Issue Type: Bug
Affects Versions: 1.5.5
Reporter: Daniel Kulp
Assignee: Daniel Kulp
Fix For: 1.5.6
With WS-SC interactions with MS WCF, MS sends back stuff like:
<o:SecurityTokenReference>
<o:Reference URI="urn:uuid:98572d85-9213-401b-8a81-e6f8b5653ef2"
ValueType="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/sct";></o:Reference>
</o:SecurityTokenReference
where the URI is the actual identifier from the SecureConversationToken (not
the wsu:Id). The ReferenceListProcessor.getKeyFromSecurityTokenReference
always does:
String uri = reference.getURI();
String id = uri.substring(1);
before calling the callback. When that happens, we cannot match the id
properly.
--
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]
