Note: This is not a fix, engineering has provided the following workaround until the product defect is fixed.
- Launch an SSH client, such as PuTTY.
- Login to the primary Authentication Manager server as rsaadmin and enter the operating system password.
Note that during Quick Setup another username may have been selected. Use that username to login.
- Change the directory to /utils.
login as: rsaadmin Using keyboard-interactive authentication. Password: Last login: Fri Dec 4 13:37:02 2020 from 192.168.20.102 RSA Authentication Manager Installation Directory: /opt/rsa/am rsaadmin@bharatham85:~> cd /opt/rsa/am/utils
- Update auth_manager.dynamic.tenant.provisioning.service.enabled from true to false using the command below, enter operations console administrator password when prompted.
./rsautil store -o <OC_admin> -a update_config auth_manager.dynamic.tenant.provisioning.service.enabled false GLOBAL 500
Snippet below
rsaadmin@bharatham85:/opt/rsa/am/utils> ./rsautil store -o ocadmin -a update_config auth_manager.dynamic.tenant.provisioning.service.enabled false GLOBAL 500 Please enter OC Administrator password: ********* psql.bin:/tmp/b67c9afa-49d4-41bd-b22d-1898680570a7268818817458797075.sql:167: NOTICE: Changed the value of configuration parameter 'auth_manager.dynamic.tenant.provisioning.service.enabled' from 'true' to 'false' for the instance 'GLOBAL'. update_config --------------- (1 row) rsaadmin@bharatham85:/opt/rsa/am/utils>
|