NetBackup™ Web UI Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring and notifications
- Section I. Configuring hosts
- Section II. Configuring storage and backups
- Configuring storage
- Managing protection plans
- Managing classic policies
- Managing backup images
- Configuring storage
- Section III. Managing credentials
- Managing credentials for workloads and systems that NetBackup accesses
- Managing credentials for workloads and systems that NetBackup accesses
- Section IV. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Managing user sessions
- Managing the security settings for the primary server
- About trusted primary servers
- Access keys
- Configuring authentication options
- Section V. Managing role-based access control
- About role-based access control in NetBackup
- Configuring RBAC roles
- Configuring RBAC
- Default RBAC roles
- Configuring RBAC
- RBAC permissions
- Global > NetBackup management
- Global > Security
- Global > Storage
- Assets
- Manage access
- Section VI. Managing detection and reporting
- Managing deployment
- Managing Resiliency Platforms
- NetBackup SaaS Protection
- NetBackup Flex Scale
- Managing Bare Metal Restore (BMR)
- Troubleshooting the NetBackup Web UI
About Single Sign-On (SSO) configuration
You can configure Single Sign-On (SSO) with any identity provider (IDP) that uses the SAML 2.0 protocol for exchanging authentication and authorization information. Note that you can configure an IDP with more than one Veritas product. For example, the same IDP can be configured with NetBackup and with APTARE.
Note the following requirements and limitations:
To use SSO, you must have a SAML 2.0 compliant identity provider configured in your environment.
Only identity providers that use AD or LDAP directory services are supported.
Configuration of the IDP requires the NetBackup APIs or the NetBackup command nbidpcmd.
SAML users cannot use the APIs. API keys are used to authenticate a user and therefore cannot be used with a SAML-authenticated user.
Global logout is not supported.