You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Scott Cantor (JIRA)" <ji...@apache.org> on 2015/02/04 19:24:36 UTC
[jira] [Commented] (SANTUARIO-414) Use standard "key names" for
Signature algorithms in the JCEMapper
[ https://issues.apache.org/jira/browse/SANTUARIO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305667#comment-14305667 ]
Scott Cantor commented on SANTUARIO-414:
----------------------------------------
That's a long bug thread, and Brent's more the authority than I am, but to be clear, OpenSAML 2.x is now in bug-fix only mode and is specifically supported only with xmlsec 1.5.x at the moment. OpenSAML 3.x is the current version, and it supports xmlsec 2.0
I don't know what the conflict at hand is, but it hasn't come up for us so far in Shibboleth.
> Use standard "key names" for Signature algorithms in the JCEMapper
> ------------------------------------------------------------------
>
> Key: SANTUARIO-414
> URL: https://issues.apache.org/jira/browse/SANTUARIO-414
> Project: Santuario
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Fix For: Java 2.0.4
>
>
> Since 2.0.x we are using the same "key name" as the JCE name for signature algorithms. This is causing an interop problem with Opensaml, see this JIRA for more information:
> https://issues.apache.org/jira/browse/CXF-6237
> Colm.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)