-
Bug
-
Resolution: Done
-
Major
-
5.0.0.Alpha7
-
None
Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration:
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<endpoint/>
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
<properties>
<property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
</properties>
</http-connector>
</subsystem>
Unfortunately, this same configuration does not work on 7.1.1. It looks
like the server still wants to use DIGEST-MD5 based authentication.
Has the legacy based configuration (non-elytron) for anonymous ejb
access changed on eap 7.1.1?
I am attaching the standalone.xml, server.log and client log.
Customer does not want to use elytron at the moment.
- clones
-
WFLY-10353 anonymous authentication for ejbs using legacy configuration - test
- Closed
- is cloned by
-
JBEAP-14778 [GSS] (7.1.z) anonymous authentication for ejbs using legacy configuration - core part
- Closed
- is related to
-
WFCORE-3963 Fix of WFCORE-3826 breaks plain authentication for ejbs using legacy configuration
- Resolved
-
WFCORE-4326 Follow up on WFCORE-3826 to add mechanism override support to the native connector.
- Resolved
- relates to
-
JBEAP-16304 [GSS](7.2.z) WFCORE-4326 - EAP 6.4 client calling EAP 7.x legacy remoting fails with server presented no authentication mechanisms when using anonymous
- Closed