-
1. Re: WildFly 13 domain mode + Elytron security domains
dlofthouse Sep 19, 2018 10:54 AM (in response to sergiu_pienar)There should not be a difference but do your ejb and undertow subsystems also have the application-security-domain mappings defined?
-
2. Re: WildFly 13 domain mode + Elytron security domains
sergiu_pienar Sep 20, 2018 7:02 AM (in response to dlofthouse)On the http-invoker I was still using the legacy realm by using <http-invoker securityRealm="acmeRealm"/> instead of the Elytron one <http-invoker http-authentication-factory="http-db-auth"/>.
However the undertow system still defines a https-listener
<https-listener name="https" socket-binding="https" security-realm="acmeRealm" enable-http2="true"/>
that seems to be making use of the legacy security configuration. Can this be upgraded to use elytron ?
I'm attaching my domain.xml.
Thanks
-
domain.xml.zip 8.8 KB
-
-
3. Re: WildFly 13 domain mode + Elytron security domains
mchoma Sep 21, 2018 1:52 PM (in response to sergiu_pienar)Sergiu, this seems as bug. Your configuration seems ok. Please could you prepare smallest possible reproducer of the problem?
-
4. Re: WildFly 13 domain mode + Elytron security domains
sergiu_pienar Sep 22, 2018 12:42 AM (in response to mchoma)Hi Martin,
I do not think this is a bug but only me not knowing what attribute replaces (that relates to elytron) the security realm attribute which I understand redirects to the legacy security system.