Administer > Configure Security > Choose a Mode for NNMi Access > X.509 Certificates to Control NNMi Access

X.509 Certificates to Control NNMi Access

The X.509 Certificate service eliminates the need for any NNMi passwords. NNMi administrators have a choice of where to define and store the required NNMi User Group membership assignments:

  • Mixed: NNMi defines and stores the User Group assignments.
  • External: NNMi uses the Lightweight Directory Access Protocol (LDAP) User Group assignments.

Tip NNMi supports Public Key Infrastructure (PKI) user authentication. This includes Smart Cards, such as Common Access Card (CAC) and Personal Identity Verification (PIV).

User Authentication Strategy
Option
Which Method for User Authentication? User Account Definitions in NNMi User Group Definitions in NNMi Which Method for Group Membership?
2 - Mixed X.509 Certificate yes yes NNMi User Account Mappings
3 - External X.509 Certificate no yes LDAP

Caution NNMi administrators must choose one Mode and configure all NNMi users with the same approach. See also:

Follow the instructions in the “Configuring NNMi to Support Public Key Infrastructure User Authentication” chapter in the Network Node Manager i Software Deployment Reference, which is available at: https://softwaresupport.softwaregrp.com/.

X.509 Certificates Configuration [These steps are in the Deployment Guide]
Mode Procedure
2 - Mixed
  1. Modify the nms-auth-config.xml file and create User Accounts as described for configuration option 2 in the “Configuring NNMi to Support Public Key Infrastructure User Authentication” chapter in the Network Node Manager i Software Deployment Reference, which is available at: https://softwaresupport.softwaregrp.com/.

  2. In the NNMi console:

    • Configure User Accounts (User Account Form).

      NNMi user names must be stored in both the X.509 Certificate implementation and the NNMi User Accounts.

      Enable the User Account form's Directory Service Account attribute to make the password unnecessary.

      Tip NNMi administrators can also add, delete, or modify NNMi user names and the Directory Service Account attribute with the nnmsecurity.ovpl command-line tool.

  3. User Groups and User Group Mappings are stored in the NNMi database:

    NNMi users can belong to more than one User Group.

    The NNMi administrator must assign each User Account to a predefined NNMi User Group before that user can access NNMi. See User Groups Provided in NNMi for more information.

  4. Configure which objects are visible to each User Group:

Note To make changes to NNMi users' user name or password, you must now use the appropriate process for making changes to the data stored in your environment's X.509 Certificate implementation.

3 - External
  1. Modify the nms-auth-config.xml file and create User Accounts as described for configuration option 2 in the “Configuring NNMi to Support Public Key Infrastructure User Authentication” chapter in the Network Node Manager i Software Deployment Reference, which is available at: https://softwaresupport.softwaregrp.com/.

  2. For this X.509 Certificate configuration, no User Accounts are required in the NNMi console:

    Configure User Accounts (User Account Form), do not use this form.

  3. User Groups are stored in the NNMi database:

  4. For this configuration, LDAP provides the User Group membership assignments. No User Account Mappings are required in the NNMi console:

    Map User Accounts to User Groups (User Account Mapping Form), do not use this form.

  5. Configure which objects are visible to each User Group:

Note To make changes to NNMi access (user name, password, or NNMi User Group assignment), you must now use the appropriate process for making changes to the data stored in your environment's X.509 Certificate implementation and directory service software.