Updating node and administrative IDs

You can update IBM Storage Protect node and administrative IDs to specify that they authenticate with an Active Directory database on a Lightweight Directory Access Protocol (LDAP) server.

About this task

Restrictions:
  • Secure Sockets Layer (SSL) communication must be enabled.
  • Do not specify a password. The password is set on the LDAP server.
  • You cannot update the authentication method for your own user ID unless you have system authority. If you do not have system authority, ask another administrator to change the authentication method.
  • Do not specify administrative IDs and node names that match. If an administrative ID matches a node name, you might see unexpected behavior because of automatic password changes that update the same password twice. As a result, the password might become unknown to the administrative ID. Alternatively, the password update operation might fail.
Specify administrative IDs by using the following format:
id@domain_name
where id represents the ID and domain_name represents the domain. For example, you can specify an administrative ID like this:
JackSpratt@us.example.com
The preferred method is to use the same format for node names; however, this format is not required.

Procedure

  1. To update an IBM Storage Protect node ID to authenticate with an LDAP server, issue the UPDATE NODE command from the IBM Storage Protect command-line interface. Specify LDAP as the authentication method:
    update node node_name authentication=ldap
    where node_name specifies the node ID.
    For example, if the node is NODE1, and the node is associated with a US company that is named EXAMPLE, issue the following command:
    update node node1@us.example.com authentication=ldap
  2. To update an IBM Storage Protect administrative ID to authenticate with the LDAP server, issue the UPDATE ADMIN command from the IBM Storage Protect command-line interface. Specify LDAP as the authentication method:
    update admin admin_name authentication=ldap
    where admin_name specifies the administrative user ID.
    For example, if the administrator name is ADMIN1, and the administrator is associated with a US company that is named EXAMPLE, issue the following command:
    update admin admin1@example.us.com authentication=ldap
  3. To change the authentication method for several node or administrator IDs, you can use a wildcard character (*).
    For example, if the node names start with AA1, issue the following command:
    update node aa1* authentication=ldap

Results

After you update a node or administrative ID to authenticate with the LDAP server, the ID will be authenticated against the Active Directory database.