[jira] [Commented] (SANTUARIO-509) XMLSignature with a specified security Provider

["sean.mullan (JIRA)" <ji...@apache.org>]

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

sean.mullan commented on SANTUARIO-509:
---------------------------------------

This doesn't directly address your use case since you are using the Apache XML Signature APIs, but if you use the standard Java SE (JSR 105) APIs, you can specify a preferred Signature provider by setting the "org.jcp.xml.dsig.internal.dom.SignatureProvider" property to the Provider in the DOMSignContext.setProperty method.

 

> XMLSignature with a specified security Provider
> -----------------------------------------------
>
>                 Key: SANTUARIO-509
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-509
>             Project: Santuario
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: Java 2.0.10, Java 2.1.4
>            Reporter: Giedrius Noreikis
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>
> Currently, it is not possible to construct and then sign or verify instances of {{org.apache.xml.security.signature.XMLSignature}} with a specified security Provider. The only way to use a custom Provider is to register it in the provider list and then specify its name in {{org.apache.xml.security.algorithms.JCEMapper}}, which is inconvenient, may fail because of security permissions, and creates problems in application servers where the same JVM is used by several applications.
> The proposal is to add constructors to {{XMLSignature}} with Provider as a parameter, like in {{java.security.Signature.getInstance()}}.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)