4.2 Understanding User Account Requirements

You need to specify a user name, password, and unique e‑mail address for the Dashboard user accounts. For more information about requirements, see the following sections:

4.2.1 Understanding User Name Restriction

A user account for the Dashboard cannot have a use name that contains the domain name managedobjects.com. The Dashboard uses this domain name for a reserved user account.

If there is a user with this domain name in the Operations Center server, it does not synchronize with the Dashboard and an error is outputted to the trace logs. For more information, see Section D.1.1, User ID Exception – Unable to Synchronize User.

4.2.2 Understanding Unique E-Mails

In order for the synchronization of users to occur in the Dashboard with the Operations Center server, the user account in Operations Center must have a unique, valid e‑mail address.

IMPORTANT:User accounts must contain a valid, unique e‑mail address to correctly synchronize between Operations Center server and the Dashboard.

A valid e‑mail address follows this pattern: _@_._ where _ is a character. A valid e‑mail address does not contain any spaces and has only one @ sign.

User accounts in the Operations Center server are not required to have e‑mail addresses. When user accounts are synchronized with the Operations Center server, if the Dashboard encounters an account without an e‑mail address, it creates an e‑mail address similar to the following:

incrementalcount@NetIQ.com

During the user synchronization, if the Dashboard encounters a user account with an e‑mail address that already matches an e‑mail address for an existing account in the Dashboard, the Dashboard attempts to address the problem by adding “generated_” to the beginning of the e‑mail address. However, if there are multiple e‑mail addresses that are the same, the Dashboard won’t be able to correct them and there will be errors.

4.2.3 Understanding Password Policy

The Dashboard uses account information including passwords from the Operations Center server. How the Operations Center server handles passwords depends on the type of account:

  • Native Accounts: In Operations Center, these accounts are stored and authenticated in the Operations Center server. For these accounts, the Operations Center administrator can set password policies.

  • External Accounts: These accounts are stored in an external directory that are authenticated using LDAP. For these accounts, Operations Center does not store any password information.

When an account is created in the Dashboard, the account is a native account in Operations Center. The Dashboard enforces the password policy for Operations Center native accounts by default. If a password is entered during the account creation that does not match the password policy, then the account is not created.

Dashboard administrators as well as the users themselves can change passwords for user accounts in the Dashboard if the account is a native account in Operations Center. The Dashboard verifies that the password follows Operations Center password policy and allows the change if it does. If it does not, the Dashboard displays an error message and the password is not changed. If the account is an external account in Operations Center, the Dashboard does not show an option to change the password.

For information on how to create user accounts and change passwords, see Section 4.4, Managing User Accounts.