To use NMS, a user has to be configured for both authentication and authorization.

Authentication (user names and passwords) for Oracle Utilities Network Management System is handled by WebLogic, and is accomplished by configuring authentication providers in WebLogic’s default security realm. This is a simplification from previous releases, where user names and passwords were kept in database tables, or where LDAP or Active Directory information had to be configured in SQL files.

Authorization (what applications a user is allowed to use, with what role or user type, or whether the user is allowed to login to the NMS at all) is handled by the Configuration Assistant. See the Configuration Assistant chapter in the Oracle Utilities Network Management System User’s Guide for more information.

Most installations will want to configure WebLogic to use an external authentication source, such as Active Directory or LDAP. These servers are often readily available on most corporate networks, they provide advantages for enforcing security policies (e.g., password complexity and aging), and the login names and passwords are already familiar to the end users. In the case that a more simple solution is required, WebLogic internal users and groups can be used to authenticate against the NMS, although this is not recommended for production environments.

Any user that appears in the users and groups in WebLogic's default security realm tab can be configured to login to NMS, with the following conditions:

Without both of these conditions being met, the application will return that the user is unauthorized.