-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR16, 7.1.0.DR18, 7.1.0.DR19
When some configuration in Elytron Client configuration file uses set-protocol then value of this element is not used for outgoing connection. Elements set-host and set-port are used correctly.
Following authentication configuration part of wildfly-config.xml should use URL remote+http://localhost:9990 for outgoing connection, but protocol remote+http from set-protocol is not used:
<authentication-configurations> <configuration name="auth-config"> <set-user-name name="user"/> <set-protocol name="remote+http"/> <set-host name="localhost"/> <set-port number="9990"/> <credentials> <clear-password password="password"/> </credentials> </configuration> </authentication-configurations>
We request blocker because this issue blocks feature for RFE EAP7-567. 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.
- duplicates
-
JBEAP-10544 Attribute protocol in authentication-configuration of Elytron subsystem is not used
- Closed
- is cloned by
-
ELY-1100 Configured set-protocol in Elytron Client configuration file is not used
- Resolved
- 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