[jboss-jira] [JBoss JIRA] (WFCORE-2315) Remoting client from EAP 7.0.0 can't authenticate against EAP 7.1.0.DR8
Darran Lofthouse (JIRA)
issues at jboss.org
Tue Feb 21 07:59:01 EST 2017
[ https://issues.jboss.org/browse/WFCORE-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse moved JBEAP-8995 to WFCORE-2315:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2315 (was: JBEAP-8995)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Remoting
Security
(was: EJB)
(was: Remoting)
(was: Security)
Affects Version/s: 3.0.0.Beta3
(was: 7.1.0.DR8)
Affects Testing: (was: Regression)
> Remoting client from EAP 7.0.0 can't authenticate against EAP 7.1.0.DR8
> -----------------------------------------------------------------------
>
> Key: WFCORE-2315
> URL: https://issues.jboss.org/browse/WFCORE-2315
> Project: WildFly Core
> Issue Type: Bug
> Components: Remoting, Security
> Affects Versions: 3.0.0.Beta3
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: authentication, eap71_alpha, regression, remoting, sasl
>
> Using dependencies from EAP 7.0.0, clients are unable to connect to EAP 7.1.0.DR8 using DIGEST-MD5 mechanism:
> {noformat}
> java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
> DIGEST-MD5: Server rejected authentication
> {noformat}
> JBOSS-LOCAL-USER method works. I'm talking about 7.1.0.DR8 with legacy security realms.
> We are supposed to maintain backward compatibility with older clients but in this case older client won't work against newer server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list