-
Title
System Administrators created via Auto Discovery can not list other System Administrator UserIDs or their own UserID or view "System Status/Settings". -
Description
A TPAM System Administrator UserID created via Auto Discovery (using the checkbox "System Administrator (like parmaster)" on the LDAP Mapping) is created as expected, and able to log in to '/admin' as expected. However, it may not be possible to return valid lists of System Administrator Users via this System Administrator UserID. Viewing the "System Status"
When trying to view "System Status" the warning "The EXECUTE permission was denied on the object 'GetSupportBundleFiles', database 'tpam', schema 'dbo'." is returned.
When trying to view "Cluster Management" the warning "The EXECUTE permission was denied on the object 'GetClusterAppliances', database 'tpam', schema 'dbo'." is returned.
When trying to add a backup Archive server, the warning "The EXECUTE permission was denied on the object 'SaveArchSrv', database 'tpam', schema 'dbo'." is returned.
There are further similar errors as this impacted user attempts to navigate through the menu system under '/admin'.
-
Resolution
WORKAROUND:
-Log into '/admin' as parmaster-make a modification to an affected SysAdmin user (add a character to the description field)-Save the change-Log in as the affected user to confirm that this SysAdmin user can now correctly listing itself and other SysAdmin users.STATUS:
NOTE: This item was listed in the 2.5.917 Release of the TPAM Appliance as being corrected; From the 2.5.917 Release Notes:
"System Administrators that use secondary authentication are not being displayed in the manage sys-admin user management listing. BFER 8706"
The above was an error in the 2.5.917 Release Notes; this fix is expected to be included in an upcoming release of TPAM.
-
Change Request
8706