-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR8, 7.1.0.DR13
-
Regression
-
-
-
-
-
-
Using dependencies from EAP 7.0.0, clients are unable to connect to EAP 7.1.0.DR8 using DIGEST-MD5 mechanism:
java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: Server rejected authentication
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.
- is cloned by
-
WFCORE-2315 Remoting client from older WildFly can't authenticate against latest WildFly Core
- Resolved
- is incorporated by
-
JBEAP-8874 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta6
- Closed
- is related to
-
JBEAP-7478 Not able to connect to EAP through jconsole from remote system
- Closed
- relates to
-
JBEAP-9555 Remote naming client from EAP 7.0 can't authenticate against EAP 7.1
- Closed