Show Table of Contents
Chapter 4. User Management
4.1. About JBoss EAP User Management
Depending on how JBoss EAP 6 is installed, there may be no user accounts initially available to access the management interfaces.
If you install the platform using a graphical installer, only one user account with the necessary privileges to access the JBoss EAP 6 management interfaces is created during the installation.
If you install the platform manually using a ZIP archive no user accounts with appropriate privileges are created during installation.
If you install the platform manually using the JAR installer at a console, one user account with appropriate privileges is created during installation.
HTTP-based communication with JBoss EAP 6 is considered remote access, even if the traffic originates on the localhost. Therefore, you must create at least one administrative user to use the management console. If you attempt to access the management console before adding a user, you will receive an error because it does not even deploy until the user is added.
This guide covers simple user management for JBoss EAP 6 using the
add-user.sh script. For more advanced authentication and authorization options, such as LDAP or Role-Based Access Control (RBAC), see the Core Management Authentication section of the JBoss EAP Security Architecture document.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.