-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
Currently, when the username attribute is not specified for a remote-outbound-connection (i.e., for the Elytron remote-outbound-connection case), the username is erroneously being treated as the string “undefined”.
- is cloned by
-
WFCORE-2809 Fix parsing and handling of the legacy username attribute for a remote-outbound-connection
- Resolved
- is incorporated by
-
JBEAP-10845 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta23
- Closed
- relates to
-
JBEAP-10610 Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context
- Closed