NetBackup™ 10.5 Application Guide
- Product overview
- Release notes
- Geting started
- Creating NetBackup application instances
- Managing NetBackup application instances
- Accessing NetBackup primary and media server instances for management tasks
- Managing users on a primary or a media server instance
- Managing multifactor authentication on a primary or a media server instance
- Running NetBackup commands on a primary or a media server application instance
- Managing users on a primary or a media server instance
- Accessing NetBackup WORM storage server instances for management tasks
- Managing users from the deduplication shell
- Managing multifactor authentication on a WORM storage server
- Managing certificates from the deduplication shell
- Configuring an isolated recovery environment using the web UI
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Managing users from the deduplication shell
Enforcing multifactor authentication on a WORM storage server
By default, multifactor authentication is optional. However, the msdpadm user can enforce it for all users on the server.
Use the following procedures to enforce or stop enforcing multifactor authentication on a WORM storage server.
To enforce multifactor authentication on a WORM storage server
- Log in to the instance as the msdpadm user.
- Run the following command:
setting MFA setenforce enforce=1 [grace_period=<days>]
Where [grace_period=<days>] is an optional parameter to specify the number of days before users are forced to configure multifactor authentication before they can log in. If you do not include this parameter, the default of 90 days is used.
For example:
setting MFA setenforce enforce=1 grace_period=30
To stop enforcing multifactor authentication on a primary or a media server instance
- Log in to the instance as the msdpadm user.
- Run the following command:
setting MFA setenforce enforce=0