-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR14
I have an remote-outbound-connection with a simple authentication configuration which I want to use for server-to-server EJB calls. Relevant configuration snippets:
<outbound-socket-binding name="remote-ejb"> <remote-destination host="${remote.ejb.host}" port="8080"/> </outbound-socket-binding> (...) <remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" authentication-context="admin-ctx"/> (...) <authentication-client> <authentication-configuration name="admin-cfg" authentication-name="admin" realm="ApplicationRealm" allow-sasl-mechanisms="DIGEST-MD5"> <credential-reference clear-text="admin123+"/> </authentication-configuration> <authentication-context name="admin-ctx"> <match-rule authentication-configuration="admin-cfg"/> </authentication-context> </authentication-client>
However, when an application tries to call remote EJBs over this connection (be it by injection via @EJB or by building an InitialContext), the authentication context doesn't seem to be applied - always only the JBOSS-LOCAL-USER mechanism is attempted and if that fails, no other mechanism is attempted.
- is blocked by
-
JBEAP-10159 Sticky authentication is not working correctly
- Closed
- is related to
-
JBEAP-10610 Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context
- Closed