-
Task
-
Resolution: Done
-
Major
-
None
-
None
Looking at the iiop testsuite module the -Delytron option maybe focussing on Elytron for SSL but I can't see where Elytron authentication is used - it feels like this may still be relying on legacy security.
/subsystem=elytron/authentication-configuration=forward-identity:add(security-domain=ApplicationDomain) /subsystem=elytron/authentication-context=default-context:add(match-rules=[{match-protocol=iiop, authentication-configuration=forward-identity}]) /subsystem=elytron:write-attribute(name=default-authentication-context, value=default-context)
<subsystem xmlns="urn:wildfly:elytron:15.0" default-authentication-context="default-context" ... > <authentication-client> <authentication-configuration name="forward-identity" security-domain="ApplicationDomain"/> <authentication-context name="default-context"> <match-rule match-protocol="iiop" authentication-configuration="forward-identity"/> </authentication-context> </authentication-client>
- causes
-
WFLY-16042 WildFly basic tests started to fail on IBM JDK11
- Closed
- is cloned by
-
JBEAP-22895 (7.4.z) WFLY-15272 - org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase needs updating to enable Elytron security
- Closed