[
https://issues.jboss.org/browse/WFCORE-2315?page=com.atlassian.jira.plugi...
]
Darran Lofthouse updated WFCORE-2315:
-------------------------------------
Description:
Using dependencies from older WildFly release, clients are unable to connect to latest
WildFly 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 latest WildFly 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.
was:
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.
Remoting client from older WildFly can't authenticate against
latest WildFly Core
---------------------------------------------------------------------------------
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 older WildFly release, clients are unable to connect to latest
WildFly 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 latest WildFly 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)