[ 
https://issues.apache.org/jira/browse/WSS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459869#comment-13459869
 ] 

Marc Giger commented on WSS-405:
--------------------------------

Implemented in r1388156 .

Colm,

Please review the changes in the DOM code. Don't hesitate to revert the commit
if you don't feel happy about it.

Notes:

1)
The new introduced constant WSConstants.KEYTRANSPORT_RSAOEP_XENC11 should 
perhaps be renamed
to WSConstants.KEYTRANSPORT_RSAOEP but this constant is already defined. A 
proper solution would be 
to rename

WSConstants.KEYTRANSPORT_RSAOEP to WSConstants.KEYTRANSPORT_RSAOEP_MGF1 and
WSConstants.KEYTRANSPORT_RSAOEP_XENC11 to WSConstants.KEYTRANSPORT_RSAOEP

2)
The DOM code does currently not support setting the oaepParams byte's (PSource) 
for encryption. But it is implemented in the decryption code. I wasn't sure how 
to do it the right way so I left it.

3)
The MGF digest algo's should probably be defined in the config.xml and 
retrieved via the JCEMapper. I've already done this in the stax code.


Marc
                
> Support for XML Encryption 1.1 algorithms
> -----------------------------------------
>
>                 Key: WSS-405
>                 URL: https://issues.apache.org/jira/browse/WSS-405
>             Project: WSS4J
>          Issue Type: Task
>          Components: WSS4J Core
>            Reporter: Marc Giger
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0
>
>
> Support for http://www.w3.org/2009/xmlenc11# algorithms like
> http://www.w3.org/2009/xmlenc11#rsa-oaep
> http://www.w3.org/2009/xmlenc11#aes256-gcm
> http://www.w3.org/2009/xmlenc11#mgf1sha256
> etc.
> in StAX and DOM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to