Elytron realm-mapper and other attributes brought by JBEAP-11177 to server-ssl-context are ignored for HTTP based authentication.

This issue follows up on JBEAP-11177 Unable to define realm-mapping for TrustManager based auth. The SASL part (which was original subject of the issue) does work with the new attributes, the HTTP part does not. The HTTP part does work with realm-mapper and other attributes in http-authentication-factory, which is against the HTTP part of statement in JBEAP-11177:

For SASL and HTTP mechanisms it is possible to define realm-mapping as part of *-authentication-factory. But this cannot be used for EXTERNAL/CLIENT_CERT mechanism, because ServerAuthenticationContext is not constructed by mechanism but by SecurityDomainTrustManager - without relation to any *-authentication-factory.

Blocker priority, like BEAP-11177.