[jira] [Reopened] (SANTUARIO-396) XMLCipher does not allow the use of Entrust RSAOAEPParamterSpec for RSA OAEP

["Kevin Urciolo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SANTUARIO-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Urciolo reopened SANTUARIO-396:
-------------------------------------


I have a potential patch that would allow individuals to plug in different implementations of the Parameter Spec generation methods.  This would allow me to work with RSA and Entrust security providers without making modifications to XMLCipher.

> XMLCipher does not allow the use of Entrust RSAOAEPParamterSpec for RSA OAEP
> ----------------------------------------------------------------------------
>
>                 Key: SANTUARIO-396
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-396
>             Project: Santuario
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: Java 1.5.7, Java 2.0.1
>         Environment: Using Entrust etjava80_8.0_Patch_190183 with Santuario 1.5.7.  Compatibility problems between two products when attempting to encrypt using Entrust security provider with RSA OAEP.
>            Reporter: Kevin Urciolo
>            Assignee: sean.mullan
>
> Similar to SANTUARIO-392, an Entrust FIPS compliant security provider for JAVA requires a RSAOAEPParameterSpec for RSA OAEP.  This prevents encryption from working since XMLCipher doesn't appear to generate this parameter spec.  Since this class is Entrust specific, it might be a good idea to allow pluggable parameter specs by algorithm URL.
> Original Exception was java.security.InvalidKeyException: Invalid parameters for an RSA cipher; only RSAOAEPParameterSpec is supported
> 	at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1443)
> 	at org.apache.xml.security.encryption.XMLCipher.encryptKey(XMLCipher.java:1382)



--
This message was sent by Atlassian JIRA
(v6.2#6252)