After the security services installation, Access Manager CLI amadmin fails with authentication login exceptions.
Workaround:
Log in to Access Manager at https://VIP:3224.
The user name and password are the values you specified during the Sun OTP installation. For example, user name can be otpadmin and password can be admin.
Select Realm—>Domain—>Authentication tab—>Advanced Properties in the Access Control tab.
Uncheck Agent under Identity type and click save config.
Disable the Access manager services on the node where changes were made for a multinode deployment.
# /usr/cluster/bin/clrg set -p RG_System=false otp-security-rg
# /usr/cluster/bin/clrs disable -n <node:zone_name> otp-ws-rs
Re-log in to at https://VIP:3224. Note that this time the URL will point to other Access Manager instance. Repeat steps 3 and 4.
Enable the Access manager services on all nodes.
# /usr/cluster/bin/clrs enable -n <node:zone_name> otp-ws-rs
# /usr/cluster/bin/clrg set -p RG_System=true otp-security-rg