Chapter 6. Security mapping to a security domain
Chapter 6. Security mapping to a security domain When you add a security mapping to a security domain, this allows you to combine authentication and authorization information after the authentication or authorization occurs, but before the information passes to the application. To add a security mapping to an existing security domain, a code , type , and relevant module options must be configured. Example: Management CLI commands for adding a SimpleRoles security mapping to an existing security domain /subsystem=security/security-domain=sampleapp/mapping=classic:add /subsystem=security/security-domain=sampleapp/mapping=classic/mapping-module=SimpleRoles:add(code=SimpleRoles,type=role,module-options=[("user1"=>"specialRole")]) reload The code field is the short name, for example SimpleRoles , PropertiesRoles , DatabaseRoles , or class name of the security mapping module. The type field refers to the type of mapping this module performs, and the allowed values are principal , role , attribute , or credential . Additional resources For more information on security mapping, see Security mapping in JBoss EAP . For a full list of the available security mapping modules and their module options, see Security mapping modules in JBoss EAP .
/subsystem=security/security-domain=sampleapp/mapping=classic:add /subsystem=security/security-domain=sampleapp/mapping=classic/mapping-module=SimpleRoles:add(code=SimpleRoles,type=role,module-options=[("user1"=>"specialRole")]) reload