Administer > Configure NNMi to Support Public Key Infrastructure User Authentication > Configuring NNMi to Restrict Certificates Used for NNMi Log On Access

Configuring NNMi to Restrict Certificates Used for NNMi Logon Access

If you are using NNMi with PKI user authentication, you might want to restrict which certificates are considered valid for NNMi logon access.

NNMi supports the following types of restrictions:

  • Restrictions on the certificate extended key usage, which can be used to restrict NNMi access to hardware-based certificates or other specific certificates.
  • Restrictions on the certificate issuer. These restrictions are intended to prevent a trusted certificate, which is loaded for purposes other than log on purposes, from being used to create log on certificates.

To configure NNMi to restrict certificates used for log on access, do the following:

  1. Edit the following file:

    Windows: %NnmDataDir%\nmsas\NNM\conf\nms-auth-config.xml

    Linux: $NnmDataDir/nmsas/NNM/conf/nms-auth-config.xml

  2. Locate the text block containing the following:

    <certificateConstraints>
  3. Use the following examples as a guide to configure NNMi to restrict certificates used for logons (replace values as appropriate):

    Example 1: To require client authentication, edit the following section:

    <!-- client authentication -->

    <extKeyUsage>1.3.6.1.5.5.7.3.2</extKeyUsage>

    Example 2: To require users to log on using a Microsoft smart card:

    <!-- Microsoft smart card logon -->

    <extKeyUsage>1.3.6.1.4.1.311.20.2.2</extKeyUsage>

    Example 3: To accept only certificates signed by a particular CA:

    <!-- Configures one or more trusted issuers. If this is configured, client certificates must be issued by one of these issuers to be used for client authentication -->

    <trustedIssuer>CN=MyIssuer, OU=MyOrgUnit, O=MyOrg, ST=CO, C=US</trustedIssuer>

    Note When multiple extKeyUsage entries are specified, the certificate must contain all of them (Boolean AND). When multiple trustIssuer entries are specified, only one must be the certificate trust issuer (Boolean OR).

  4. Run the following command for the change to take effect:

    nnmsecurity.ovpl -reloadAuthConfig