-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR16, 7.1.0.DR18, 7.1.0.DR19
When authentication-configuration in Elytron subsystem uses attribute protocol then value of this attribute is not used for outgoing connection. Attributes host and port are used correctly.
Following authentication-configuration of Elytron subsystem should use URL remote+http://localhost:9990 for outgoing connection, but protocol remote+http from protocol is not used:
<authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990"> <credential-reference clear-text="pass@123"/> </authentication-configuration>
We request blocker because this issue blocks feature for RFE EAP7-568. Due to issue incorrect protocol can be unexpectedly used for outgoing connection, e.g. http can be used instead of https.
This issue is blocker for GA, not for testing.
- is blocked by
-
ELY-1102 Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol
- Resolved
- is caused by
-
REM3-270 AuthenticationConfiguration protocol is not being used
- Resolved
- is cloned by
-
WFCORE-2724 Attribute protocol in authentication-configuration of Elytron subsystem is not used
- Resolved
- is duplicated by
-
JBEAP-10543 Configured set-protocol in Elytron Client configuration file is not used
- Closed
- is incorporated by
-
JBEAP-10845 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta23
- Closed
-
JBEAP-11280 Upgrade remoting to 5.0.0.Beta25
- Closed