You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2009/01/27 17:16:59 UTC
[jira] Updated: (WSS-156) Add support for RSAKeyValue
tokens/signatures (needed for WS-SecurityPolicy KeyValueToken)
[ https://issues.apache.org/jira/browse/WSS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated WSS-156:
------------------------------------
Fix Version/s: 1.5.6
> Add support for RSAKeyValue tokens/signatures (needed for WS-SecurityPolicy KeyValueToken)
> ------------------------------------------------------------------------------------------
>
> Key: WSS-156
> URL: https://issues.apache.org/jira/browse/WSS-156
> Project: WSS4J
> Issue Type: New Feature
> Components: WSS4J Core
> Affects Versions: 1.5.5
> Reporter: Daniel Kulp
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.6
>
>
> To support scenario 9 of the MS InteropPlugFest stuff for WS_Trust13, we need to have the WS-SecurityPolicy KeyValueToken stuff working. Right now, there isn't a way in WSS4J to produce a signature with the embedded RSAKeyValue. It should look like:
> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
> <SignedInfo>
> <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod>
> <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod>
> <Reference URI="#_0">
> <Transforms>
> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform>
> </Transforms>
> <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></DigestMethod>
> <DigestValue>gooGYO8hV6p5uAokx1bRD+oXTE0=</DigestValue>
> </Reference>
> <Reference URI="#_1">
> <Transforms>
> <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform>
> </Transforms>
> <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></DigestMethod>
> <DigestValue>8+/r6H6VGm1AoYQGAGzqT8dmlxA=</DigestValue>
> </Reference>
> </SignedInfo>
> <SignatureValue>cu4ESQndScNrg0VlV83HbkQJJA2IQHE3hyo5B7pbYWNUURSexZKJR3m0Bt7AFvBPuMqatImqWevrHhL85RZQ8RMHXwnjwcjdiL3f8HZqK1sqtg5cFBa4ayNC9lXohwd1McUZIZCE/3RpStWxiPQXa/bV0gh4qAl2tyG4VsMtLZU=</SignatureValue>
> <KeyInfo>
> <KeyValue>
> <RSAKeyValue>
> <Modulus>h/zOuD1JepECJhiCYD5ycAsj3K/W30VDNukBdGLe61dNp7VB4Iqo0SmVqS7PNzfcChhUyg+6/O8BlTIDQ8n3tQ/5sTduaaeaj8pjYICR8U79Es6aHx8hXrw7YoQK3uA8Bnu/xK4n7sN4xowjXcCbmlLuGyaRRk+dOCnV2r1Hhw8=</Modulus>
> <Exponent>AQAB</Exponent>
> </RSAKeyValue>
> </KeyValue>
> </KeyInfo>
> </Signature>
>
--
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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org