Article Content
Article Number | 000031057 | ||||||
Applies To | RSA Product Set: SecurID RSA Product/Service Type: Authentication Manager Prime RSA Version/Condition: All versions | ||||||
Issue | HelpDesk Admin Portal (HDAP) log file reports: 2015-08-26T11:21:05,303+1000,70953139 [http-bio-8282-exec-6] ERROR com.rsa.pso.lap.web.UtilityBean - getPermissions() => hdapadmin is not assigned to any administrative roles that support allow access to hdap. Contact your administrator to grant access to hdap 2015-08-26T11:21:05,303+1000,70953139 [http-bio-8282-exec-6] ERROR com.rsa.pso.lap.web.UtilityBean - Exception occured sending status code 403/com.rsa.pso.exception.UnAuthorizeException: You are not authorized to view this page 2015-08-26T11:21:05,303+1000,70953139 [http-bio-8282-exec-6] ERROR com.rsa.pso.lap.web.UtilityBean - Exception occured sending status code 403/java.lang.Exception HelpDesk Admin Portal (HDAP) logon fails with a message 'You are not authorized for the operation.' Example: ![]() | ||||||
Cause | HelpDesk Admin Portal (HDAP) use authentication manager administrative roles defined in the Security Console to map claims for HDAP administrative users. The role names defined in the <HDAP_home>/config/lapProto.xml file do not must match the administrative roles defined in the Security Console. | ||||||
Resolution | With an administrative account for the Security Console add the administrative role that matches the name of the role name used by the Helpdesk Admin Portal. Example: ![]() An administrative role is a collection of permissions that can be assigned to an administrator. A role determines what level of control the administrator has over users, user groups, and so on. You can add administrative roles to your deployment, and assign these roles to users. If you assign multiple administrative roles to a user, the permissions are combined. Before You Begin To create an administrative role, you must have an administrative role that:
| ||||||
Notes | Contacting RSA Customer Support
|