For scenarios like this, we must reset the super's password in the backend database in which PAM is leveraging. Please raise a Support case and request for SSH Debug patch.
You need to apply the PAM_SUPPORT_SSH_DEBUG.p.bin patch:
- Logon to PAM as super
- Configuration > Upgrade > upload and apply PAM_SUPPORT_SSH_DEBUG.p.bin
- Configuration > Diagnostics > System - > Turn ON Remote CA PAM Debugging Services
- Launch PuTTY, create a new SSH connection to the PAM server and set SSH_DEBUG_<date>.ppk file (contained in SSH DEBUG patch zip file) into
Connection > SSH > Auth > Private Key for authentication
Please test the SSH connection is successful - you should see the following prompt
Once this is all in place, request Support engineer to logging into the PAM appliance and injecting a few SQL queries to reset super's password.