WildFly Security Realms
External
- RedHat Documentation Security Guide https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Security_Guide/index.html#chap-Security_Realms
- jboss.org Security Realms Article https://docs.jboss.org/author/display/AS71/Security+Realms
Internal
Overview
A security realm is a WildFly-specific identity store of usernames, passwords and group membership information that can be used to authenticate users of the management interfaces, web applications and EJBs.
The security realm contains mappings between users and passwords, and users and roles - a mechanism for adding authentication and authorization to applications and JBoss management facilities and regular applications.
By default WildFly comes pre-configured with two realms:
Both of these use filesystem-based stores for users and group membership, and use a digest mechanism by default when authenticating.
New security realms can be configured. See Adding a New Security Realm.
The existing security realms can be reconfigured to use other authentication mechanisms, different from digest.
Security realms are not involved in any authorization decisions, however they can be configured to load a user's group membership information, which then can be subsequently used to make authorization decisions. The user is authenticated first, then the group membership information is loaded as part of a second step.
The management interfaces and the associates security realms are loaded as core services.
For a better upper level picture of WildFly security, see WildFly Security Concepts.
Relationship between a Security Realm and a Security Domain
The Digest Mechanism
The digest mechanism (DIGEST-MD5) used by the WildFly security realms is an authentication mechanism that authenticates the user by computing one-time, one-way hashes comprised of various pieces of information, including information stored in the users/passwords mapping property file. This allows WildFly to authenticate users without sending any passwords in plain text over network.
The user file contains the mapping between the user name and the password hash.
When a user attempts to authenticate, WildFly sends a one-time use number (nonce) to the client. The client generates a one-way has using their username, password, nonce and few other fields, and sends to WildFly instance the username, nonce and one-way hash. WildFly looks up the users's password hash and uses it along with the provided username, nonce and few other fields to generate another one-way hash in the same manner. If the hashes match, the user is authenticated.
This is how a JBoss Remoting client performs a programmatic login:
Local File-Based Authentication Mechanism
JBoss has a local file-based authentication mechanism, also known as the "LOCAL" authentication mechanism, based on the fact that a local client has access to a file created by the server on the local file system, specifically in the $JBOSS_HOME/standalone/tmp/auth directory. If the client can read the file, then the username/password is not used and the local file-based authentication serves as the only authentication. The name of the user authenticated as such is specified in the configuration, and it is by default "$local". The "LOCAL" mechanism automatically authenticates all local users, if configured, and is specifically provided for local tools running against this AS installation, form the same host, such as the CLI.
Note that LOCAL authentication only works if jboss-cli.sh is run by the same UNIX user that runs the host controller.
Local File-Based Authentication Configuration
The LOCAL authentication mechanism can be configured under the <authentication> section of the <security-realm> configuration:
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<local default-user="$local" skip-group-loading="true"/>
...
</authentication>
...
</security-realm>
</security-realms>
</management>
Both the Management Realm and Application Realm allow local file-based authentication, if they are configured as shown above. For more details see Management API Configuration. Once connected via CLI, the identity can be confirmed as follows:
:whoami
{
"outcome" => "success",
"result" => {"identity" => {
"username" => "$local",
"realm" => "ManagementRealm"
}}
}
Local authentication is automatically disabled if a user is specified when connecting the CLI.
Management Realm
The management realm stores authentication and authorization information for the management API. Further authentication mechanism can be configured as part of the <management> element in host.xml or standalone.xml. For more details see Management API Configuration - Management Realm Configuration Files.
The management realm allows LOCAL authentication if configured as described here: Local File-Based Authentication Configuration.
Application Realm
The application realm stores authentication and authorization information for the deployed applications (web applications and EJBs).
The management realm allows LOCAL authentication if configured as described here: Local File-Based Authentication Configuration.
For more details see Management API Configuration - Application Realm Configuration Files.
Adding a New Security Realm
Adding Users to Security Realms
Organizatorium
- TODO: define org.jboss.as.domain.management.AuthenticationMechanism: LOCAL, CLIENT_CERT, DIGEST, PLAIN;