[jboss-jira] [JBoss JIRA] (WFLY-6304) Remoting login module's certificate propagation uses the old certificate API but should be using the new API instead
Darran Lofthouse (JIRA)
issues at jboss.org
Tue Mar 1 07:27:00 EST 2016
[ https://issues.jboss.org/browse/WFLY-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse updated WFLY-6304:
-----------------------------------
Labels: deprecated (was: )
> Remoting login module's certificate propagation uses the old certificate API but should be using the new API instead
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6304
> URL: https://issues.jboss.org/browse/WFLY-6304
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.Final
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Priority: Minor
> Labels: deprecated
>
> RemotingLoginModule propagates javax.security.cert.X509Certificate but should use the newer API java.security.cert.X509Certificate.
> David proposed the following:
> The problem is at org.jboss.as.security.remoting.RemotingLoginModule line 126: session.getPeerCertificateChain() is called where session.getPeerCertificates() should be.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list