WildFly Security Domains: Difference between revisions
| Line 9: | Line 9: | ||
Security domains are declared in the JBoss configuration files ([[domain.xml]] or [[standalone.xml]]) as part of the [[WildFly Security Subsystem Concepts|security subsystem]]. Since the security domains are part of the security subsystem, they are loaded after [[WildFly_Core_Services|core services]]. | Security domains are declared in the JBoss configuration files ([[domain.xml]] or [[standalone.xml]]) as part of the [[WildFly Security Subsystem Concepts|security subsystem]]. Since the security domains are part of the security subsystem, they are loaded after [[WildFly_Core_Services|core services]]. | ||
Users can create custom security domains, as shown here | Users can create custom security domains, as shown here [[WildFly_Security_Subsystem_Configuration#Adding_a_New_Security_Domain|Adding a New Security Domain]] | ||
Revision as of 20:53, 6 March 2017
Internal
Overview
A security domain is a set of Java Authentication and Authorization Service (JAAS) declarative security configurations used by one or more applications to control authentication, authorization and security auditing. An application specifies a security domain to manage its security information. Security domains are declared as part of the security subsystem. A security domain is a JBoss concept that predates the security realm, which was introduced in JBoss 7 and then WildFly.
Security domains are declared in the JBoss configuration files (domain.xml or standalone.xml) as part of the security subsystem. Since the security domains are part of the security subsystem, they are loaded after core services.
Users can create custom security domains, as shown here Adding a New Security Domain