To configure SAML keystore and add and enable an IDP configuration

1. Log on to the primary server as root or administrator.
2. Run the following command.

   For IDP and NetBackup CA SAML KeyStore configuration:

   nbidpcmd -ac -n IDP configuration name -mxp IDP XML metadata file [-t SAML2] [-e true | false] [-u IDP user field] [-g IDP user group field] [-cCert] [-f] [-M primary server]

   Alternatively for IDP and ECA SAML KeyStore configuration:

   Depending on whether you want to configure SAML ECA KeyStore using the configured NetBackup ECA KeyStore or you want to provide the ECA certificate chain and private key, run the following commands:

   • Use NetBackup ECA configured keystore:

     nbidpcmd -ac -n IDP configuration name -mxp IDP XML metadata file[-t SAML2] [-e true | false] [-u IDP user field] [-g IDP user group field] -cECACert -uECA existing ECA configuration [-f] [-M Primary Server]

   • Use ECA certificate chain and private key provided by the user:

     nbidpcmd -ac -n IDP configuration name -mxp IDP XML metadata file[-t SAML2] [-e true | false] [-u IDP user field] [-g IDP user group field] -cECACert -certPEM certificate chain file -privKeyPath private key file [-ksPassPath KeyStore passkey file] [-f] [-M primary server]

   Replace the variables as follows:

   • IDP configuration name is a unique name provided to the IDP configuration.

   • IDP XML metadata file is the path to the XML metadata file, which contains the configuration details of the IDP in Base64URL-encoded format.

   • -e true | false enables or disables the IDP configuration. An IDP configuration must be added and enabled, otherwise users cannot sign in with the single sign-on (SSO) option. Even though you can add multiple IDP configurations on a NetBackup primary server, only one IDP configuration can be enabled at a time.

   • The SAML attribute names IDP user field and IDP user group field are used to map user identity information and group information in the Identity Provider. These fields are optional, and if not provided, they are mapped to the userPrincipalName and memberOf SAML attributes by default.

     For instance, if you have customized the attribute mapping in the Identity Provider to use attributes like email and groups, when configuring the SAML configuration, you need to provide the -u option for email and -g option for groups.

     If you have not provided values for these attributes during configuration, ensure that the Identity Provider returns the values against the userPrincipalName and memberOf attributes.

     For Example:

     If SAML response is as follows:

     saml:AttributeStatement <saml:Attribute Name="userPrincipalName"> <saml:AttributeValue>username@domainname</saml:AttributeValue> </saml:Attribute> <saml:Attribute Name="memberOf"> <saml:AttributeValue>CN=group name, DC=domainname</saml:AttributeValue> </saml:Attribute> </saml:AttributeStatement>

     It implies that you need to map the -u and -g options against the fields "saml:Attribute Name".

     Note:

     Ensure that the SAML attribute values are returned in the format of username@domainname for the field mapped to the -u option that defaults to userPrincipalName. If you include the domain name when returning group information, it should follow the format "(CN=group name, DC=domainname)" or "(domainname\groupname).

     However, if you return the group name as plain text without domain information, it should be mapped without the domain name in the SAML RBAC group.

   • primary Server is the host name or IP address of primary server to which you want to add or modify the IDP configuration. The NetBackup primary server where you run the command is selected by default.

   • Certificate Chain File is the certificate chain file path. The file must be in PEM format and must be accessible to the primary server on which the configuration is being performed.

     Private Key File is the private key file path. The file must be in PEM format and must be accessible to the primary server on which the configuration is being performed.

     KeyStore Passkey File is the KeyStore passkey file path and must be accessible to the primary server on which the configuration is being performed.

   If your Identity Provider is already configured with SAML attribute names as userPrincipalName and memberOf, you do not have to provide the -u and -g option while configuration. If you are using any other custom attributes name, provide those names against -u and -g as follows:

   For example:

   If the Identity Provider SAML attribute names are mapped as "email" and"groups", use the following command for configuration:

   nbidpcmd -ac -n cohesity_configuration -mxp file.xml -t SAML2 -e true -u email -g groups -cCert -Mprimary_server.abc.com

   -u and -g are optional and it depends on the Identity Provider configuration. Ensure that you specify the same parameter values that you have provided at the time of configuration.