[
https://issues.apache.org/jira/browse/WSS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703553#action_12703553
]
Colm O hEigeartaigh commented on WSS-179:
-----------------------------------------
Using Direct Reference will be supported. This is a sample output:
<wsse:SecurityTokenReference wsu:Id="STRId-7552289AD35BE72EE512409111235516">
<wsse:Reference URI="#EncKeyId-7552289AD35BE72EE512409111235514"
ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey"/>
</wsse:SecurityTokenReference>
This is all being supported programatically though, I'm not sure if it'll be
feasible to support this kind of behaviour through configuration.
> Allow signature using a symmetric key and EncryptedKeySHA1
> ----------------------------------------------------------
>
> Key: WSS-179
> URL: https://issues.apache.org/jira/browse/WSS-179
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 1.5.7
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.8, 1.6
>
>
> This task is to allow WSSecSignature to take in a SecretKey object or an
> array of bytes representing a symmetric key, and use it to sign data. The key
> will be referenced using EncryptedKeySHA1.
--
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]
