Veritas NetBackup™ Virtual Appliance Documentation
- Getting to know the NetBackup Virtual Appliance
- NetBackup Virtual Appliance product description
- Preparing to deploy the appliance
- Deploying and configuring the appliance
- How to deploy and configure a NetBackup Virtual Appliance combined master and media server
- How to deploy and configure a NetBackup Virtual Appliance media server
- How to deploy and configure a NetBackup Virtual Appliance master server
- How to deploy and configure a NetBackup Virtual Appliance CloudCatalyst
- How to deploy and configure a NetBackup Virtual Appliance combined master and media server
- Post initial configuration procedures
- Appliance common tasks
- Storage management
- About NetBackup Virtual Appliance storage configuration
- About viewing storage space information using the Show command
- About OpenStorage plugin installation
- About NetBackup Virtual Appliance storage configuration
- Deduplication pool catalog backup and recovery
- Network connection management
- Managing users
- About user name and password specifications
- About authenticating LDAP users
- About authenticating Active Directory users
- About authenticating Kerberos-NIS users
- About user authorization on the NetBackup Virtual Appliance
- Creating NetBackup administrator user accounts
- Using the appliance
- About configuring Host parameters for your appliance on the NetBackup Virtual Appliance
- About Copilot functionality and Share management
- About NetBackup Virtual Appliance as a VMware backup host
- About running NetBackup commands from the appliance
- About mounting a remote NFS
- About Auto Image Replication from a NetBackup Virtual Appliance
- Monitoring the appliance
- About SNMP
- About Call Home
- Appliance security
- About Symantec Data Center Security on the NetBackup Virtual Appliance
- Setting the appliance login banner
- Upgrading the appliance
- About upgrading to NetBackup Virtual Appliance software version 3.2
- Requirements and best practices for upgrading NetBackup appliances
- Methods for downloading appliance software release updates
- NetBackup client upgrades with VxUpdate
- Appliance restore
- Decommissioning and Reconfiguring
- Troubleshooting
- About disaster recovery
- About NetBackup support utilities
- Appliance logging
- Commands overview
- Appendix A. Appliance commands
- Appendix B. Manage commands
- Appendix C. Monitor commands
- Appendix D. Network commands
- Appendix E. Reports commands
- Appendix F. Settings commands
- Appendix G. Support commands
About authentication using smart cards and digital certificates
The NetBackup Web UI supports authentication of Active Directory (AD) or Lightweight Directory Access Protocol (LDAP) domain users with a digital certificate or smart card, including CAC and PIV. This authentication method only supports one AD or LDAP domain for each appliance master server domain and is not available for local domain users. You must configure LDAP for NetBackup, even if LDAP is already configured on the appliance.
Note:
Perform this configuration separately for each appliance master server domain where you want to use this authentication method.
Ensure that you add the AD or the LDAP domain before you add access rules for domain users or configure the domain for smart card authentication. Use the vssat command to add AD or LDAP domains.
To add the AD or the LDAP domain for NetBackup
- Log on to the appliance master server as a NetBackupCLI user.
- Run the vssat command.
vssat addldapdomain -d DomainName -s server_URL -u user_base_DN -g group_base_DN -t schema_type -m admin_user_DN
Replace the variables in the above command as per the following descriptions:
DomainName is a symbolic name that uniquely identifies an LDAP domain.
server_URL is the URL of the LDAP directory server for the given domain. The LDAP server URL must start with either
ldap://
orldaps://
. Starting withldaps://
indicates that the given LDAP server requires SSL connection. For exampleldaps://my-server.myorg.com:636
.user_base_DN is the LDAP-distinguished name for the user container. For example,
ou=user,dc=mydomain,dc=myenterprise,dc=com
.group_base_DN is the LDAP-distinguished name for the group container. For
example, ou=group,dc=mydomain,dc=myenterprise,dc=com
.schema_type specifies which type of LDAP schema to use. The two default schema types that are supported are rfc2307 or msad.
admin_user_DN is a string that contains the DN of the administrative user or any user that has search permission to the user container, or user subtree as specified by UserBaseDN. If the user container is searchable by anyone including an anonymous user, you can configure this option as an empty string. For example, --admin_user=. This configuration allows anyone to search the user container.
- Verify that the specified AD or LDAP domain was successfully added using vssat validateprpl. Note that you can also use the vssat command with the following options:
vssat removeldapdomain removes an LDAP domain from the authentication broker.
vssat validategroup checks the existence of a user group in domain provided.
vssat validateprpl checks the existence of a user in domain provided.
For more details on the vssat command, see the Veritas NetBackup Commands Reference Guide
After adding the AD and LDAP domains for NetBackup, you can use the nbasecadmin user to log on to the NetBackup Web UI and configure role-based access control for the NetBackup web UI. For more information about configuring RBAC for NetBackup Virtual Appliance users, see the NetBackup Web UI Security Administrator's Guide.
You can use the nbasecadmin user to log on to the NetBackup Web UI and configure authentication for a smart card or digital certificate. Refer to the NetBackup Web UI Security Administrator's Guide for steps on performing the following procedures required for the configuration:
Configure NetBackup Web UI to authenticate users with a smart card or digital certificate.
Edit the configuration for smart card authentication.
Add a CA certificate that is used for smart card authentication.
Delete a CA certificate that is used for smart card authentication.