The mapping-module option "module" in a security-domain is dissapearing

Solution Verified - Updated -

Issue

We created a custom mapping-module, installed it as a JBoss module, and configured it in a security domain.

<security-domain name="accept-all" cache-type="default">
   <authentication>
    ...
   </authentication>
   <mapping>
    <mapping-module code="our.security.mappingmoduleCode" type="role" module="our.mappingmodule">
      <module-option name="roles" value="ALLOW-ALL"/>
    </mapping-module>
</mapping>
</security-domain>

When JBoss starts, the module gets loaded just fine.
As soon as we make a configuration change that makes JBoss rewrite the configuration to standalone.xml (domain.xml) the "module" option is gone and a subsequent start of JBoss fails.

Environment

JBoss Enterprise Application Platform (EAP) 6.0.0, 6.0.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.