Disabling the default admin user
If you are using an enterprise-grade LDAP server for user management, you can further secure your Cloud Pak for Data system by disabling the default admin user.
Before you begin
Best practice: You can run the commands in
this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.
Ensure that you source the environment variables before you run the commands in this task.
The admin must switch control of catalogs and categories to other users by performing the following tasks. If you don't complete these tasks, no one will be able to administer the catalogs or categories.
Action | Required if... | Instructions |
---|---|---|
Add at least one other collaborator with the Admin role to these catalogs:
|
This action is required if either of these services are installed:
|
Managing catalog collaborators |
Add at least one collaborator with the Owner role to these categories:
|
This action is required only if Watson Knowledge Catalog is installed. | Managing category collaborators |
Procedure
To disable the default admin user:
What to do next
To re-enable the default admin user:
- Log in to your Red Hat
OpenShift cluster as a
project
administrator:
oc login ${OCP_URL}
- Run the following
command:
oc exec -it -n ${PROJECT_CPD_INSTANCE} \ $(oc get pod -n ${PROJECT_CPD_INSTANCE} -l component=usermgmt | tail -1 | cut -f1 -d\ ) \ -- bash -c "/usr/src/server-src/scripts/manage-user.sh --enable-user admin"
- When prompted, specify a new password for the admin user.