When creating a new system in TPAM you may notice that for certain platforms there are multiple types to choose from, for example.
The different types are there to handle different platform configurations since they each handle passwords in different ways. It has been our experience that the PAR administrator isn’t always fully versed in the nuances of all the managed platforms TPAM is able to manage. In certain instances when a managed system was added to the TPAM appliance the wrong platform was selected. For example, HP-UX instead of HP-UX Untrusted. For both platforms, the command used to change the password is the same but the location of where the password is stored is different. You would see the successful reset of a password but when the password was tested/checked the appliance would look in the wrong location on the managed system for the password file (/tcb/files/auth/*/* instead of /etc/passwd) and the appliance would report a password mismatch
When troubleshooting managed account/managed system issues it’s important to perform a test on the system and then review the results, perform a reset password of a managed account and review the results, and perform a check password and looking through the results. For most Linux/UNIX platforms when there is an issue the results walk you through the connection process and will typically shed the most light on what the issue might be.