You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (Jira)" <ji...@apache.org> on 2019/08/30 11:40:00 UTC
[jira] [Updated] (SANTUARIO-509) XMLSignature with a specified
security Provider
[ https://issues.apache.org/jira/browse/SANTUARIO-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated SANTUARIO-509:
------------------------------------------
Fix Version/s: Java 2.1.5
> 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
> Fix For: Java 2.1.5
>
>
> 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
(v8.3.2#803003)