Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Web UI Administrator's Guide
  3. Section IX. Managing security
  4. Configuring authentication options
  5. Troubleshooting SSO
  6. Unable to sign in due to authorization-related issues
NetBackup™ Web UI Administrator's Guide

Unable to sign in due to authorization-related issues

To sign in with SSO, you must add SAML users and the SAML user groups to the necessary RBAC roles. If the RBAC roles are not correctly assigned, you might encounter the following error while signing into NetBackup web UI.

You are not authorized to access this application. Contact your NetBackup security administrator to request RBAC permissions for the NetBackup web user interface.

Refer to the table below to troubleshoot authorization-related issues:

Table:

Cause

Explanation and recommended action

RBAC roles are not assigned to the SAML users and the SAML groups.

After an IDP configuration is added and enabled on the NetBackup primary server, ensure that necessary RBAC roles are assigned to SAML users and SAML user groups that use SSO. Note that SAML users and SAML user groups are available in RBAC only after the IDP configuration is added and enabled on the NetBackup primary server.

For steps on adding users, See Add a user to a role (non-SAML).

RBAC roles are assigned to SAML users and SAML user groups associated with an IDP configuration that is not currently added and enabled.

When you add a SAML users or SAML user group in RBAC, the SAML user or SAML user group entry is associated with the IDP configuration that is added and enabled at that time.

If you add and enable a new IDP configuration, ensure that you also add another entry for the SAML user or SAML user group. The new entry is associated with the new IDP configuration.

For example, NBU_user is added to RBAC and assigned the necessary permissions, while an ADFS IDP configuration is added and enabled. If you add and enable an Okta IDP configuration, you must add a new user entry for NBU_user. Assign the necessary RBAC roles to the new user entry, which is associated with the Okta IDP configuration.

For steps on adding users, See Add a user to a role (non-SAML).

RBAC roles are assigned to local domain users or Active Directory (AD) or LDAP domain users (instead of SAML users and SAML user groups).

SAML user or SAML user group records might appear similar to corresponding local domain users or AD or LDAP domain users already added in the RBAC.

After an IDP configuration is added and enabled on the NetBackup primary server, ensure that you add SAML users and SAML user groups in RBAC and assign the necessary permissions. Note that SAML users and SAML user groups are available in RBAC only after the IDP configuration is added and enabled on the NetBackup primary server.

For steps on adding SAML users and user groups, See Add a user to a role (non-SAML).

The NetBackup primary server is unable to retrieve user group information from the IDP

The IDP sends SAML responses to the NetBackup primary server, which contains SAML user and SAML user group information. To enable the IDP to successfully send this information, ensure the following:

  • The IDP is configured to authenticate domain users from AD or LDAP.

  • The value of memberOf attribute sent by the IDP is in the X.500 distinguished format, that is, {cn=groupname,dc=domain}.

  • While adding the IDP configuration to the NetBackup primary server, the values entered for the user group (-g) option matches the SAML attribute name, which is mapped to the memberOf attribute in AD or LDAP. For more information, See Configure the SAML keystore and add and enable the IDP configuration.

Feedback

Was this page helpful?
Previous

Redirection issues

Next

Managing role-based access control (RBAC)

Feedback

Was this page helpful?