Worksheets for administrator authentication and RBAC configuration
Before creating login accounts and setting up role-based access control (RBAC), you should gather information for each item in the configuration worksheets.
Create or modify login accounts
You provide these values with the security login create
command when you enable login accounts to access a storage VM. You provide the same values with the security login modify
command when you modify how an account accesses a storage VM.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM that the account accesses. The default value is the name of the admin storage VM for the cluster. |
|
|
The user name or group name of the account. Specifying a group name enables access to each user in the group. You can associate a user name or group name with multiple applications. |
|
|
The application that is used to access the storage VM:
|
|
|
The method that is used to authenticate the account:
|
|
|
The IP address of the remote switch. The remote switch can be a cluster switch monitored by the cluster switch health monitor (CSHM) or a Fibre Channel (FC) switch monitored by the MetroCluster health monitor (MCC-HM). This option is applicable only when the application is |
|
|
The access control role that is assigned to the account:
|
|
|
(Optional) Descriptive text for the account. You should enclose the text in double quotation marks ("). |
|
|
Whether the account is an LDAP group account or NIS group account ( |
|
|
Second authentication method in case of multifactor authentication:
The order of authentication is always the public key followed by the password. |
|
|
Beginning with ONTAP 9.11.1, when set to true, enables LDAP fast bind for nsswitch authentication; the default is false. To use LDAP fast bind, the |
Configure Cisco Duo security information
You provide these values with the security login duo create
command when you enable Cisco Duo two-factor authentication with SSH logins for a storage VM.
Field |
Description |
Your value |
---|---|---|
|
The storage VM (referred to as a vserver in the ONTAP CLI) to which the Duo authentication settings apply. |
|
|
Your integration key, obtained when registering your SSH application with Duo. |
|
|
Your secret key, obtained when registering your SSH application with Duo. |
|
|
The API hostname, obtained when registering your SSH application with Duo. For example: api-<HOSTNAME>.duosecurity.com |
|
|
On service or configuration errors that prevent Duo authentication, fail |
|
|
Use the specified HTTP proxy. If the HTTP proxy requires authentication, include the credentials in the proxy URL. For example: http-proxy=http://username:password@proxy.example.org:8080 |
|
|
Either When configured with |
|
|
If a user fails to authenticate with a second factor, Duo prompts the user to authenticate again. This option sets the maximum number of prompts that Duo displays before denying access. Must be For example, when When configured with For the best experience, a user with only publickey authentication will always have |
|
|
Enable Duo two-factor authentication. Set to |
|
|
This option provides additional information in the push notification, such as the name of the application or service being accessed. This helps users verify that they are logging in to the correct service and provides an additional layer of security. |
Define custom roles
You provide these values with the security login role create
command when you define a custom role.
Field |
Description |
Your value |
---|---|---|
|
(Optional) The name of the storage VM (referred to as a vserver in the ONTAP CLI) that is associated with the role. |
|
|
The name of the role. |
|
|
The command or command directory to which the role gives access. You should enclose command subdirectory names in double quotation marks ("). For example, |
|
|
(Optional) The access level for the role. For command directories:
For nonintrinsic commands (commands that do not end in
To grant or deny access to intrinsic commands, you must specify the command directory. |
|
|
(Optional) The query object that is used to filter the access level, which is specified in the form of a valid option for the command or for a command in the command directory. You should enclose the query object in double quotation marks ("). For example, if the command directory is |
Associate a public key with a user account
You provide these values with the security login publickey create
command when you associate an SSH public key with a user account.
Field |
Description |
Your value |
---|---|---|
|
(Optional) The name of the storage VM that the account accesses. |
|
|
The user name of the account. The default value, |
|
|
The index number of the public key. The default value is 0 if the key is the first key that is created for the account; otherwise, the default value is one more than the highest existing index number for the account. |
|
|
The OpenSSH public key. You should enclose the key in double quotation marks ("). |
|
|
The access control role that is assigned to the account. |
|
|
(Optional) Descriptive text for the public key. You should enclose the text in double quotation marks ("). |
|
|
(Optional) Beginning with ONTAP 9.13.1, enables you to manage X.509 certificate association with the SSH public key. When you associate an X.509 certificate with the SSH public key, ONTAP checks upon SSH login to see if this certificate is valid. If it has expired or been revoked, login is disallowed and the associated SSH public key is disabled. Possible values:
|
Configure dynamic authorization global settings
Beginning with ONTAP 9.15.1, you provide these values with the security dynamic-authorization modify
command. For more information about dynamic authorization configuration, refer to dynamic authorization overview.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM for which the trust score setting should be modified. If you omit this parameter, the cluster-level setting is used. |
|
|
The dynamic authorization mode. Possible values:
|
|
|
Prevents additional authentication challenges within the specified interval. The interval is in ISO-8601 format and accepts values from 1 minute to 1 hour inclusive. If set to 0, the suppression interval is disabled and the user is always prompted for an authentication challenge if one is needed. |
|
|
The lower multi-factor authentication (MFA) challenge percentage boundary. The valid range is from 0 to 99. The value 100 is invalid, because this causes all requests to be denied. The default value is 0. |
|
|
The upper MFA challenge percentage boundary. The valid range is from 0 to 100. This must be equal to or greater than the value of the lower boundary. A value of 100 means that every request will either be denied or subject to an additional authentication challenge; there are no requests that are allowed without a challenge. The default value is 90. |
Install a CA-signed server digital certificate
You provide these values with the security certificate generate-csr
command when you generate a digital certificate signing request (CSR) for use in authenticating an storage VM as an SSL server.
Field |
Description |
Your value |
---|---|---|
|
The name of the certificate, which is either a fully qualified domain name (FQDN) or a custom common name. |
|
|
The number of bits in the private key. The higher the value, the more secure the key. The default value is |
|
|
The country of the storage VM, in a two-letter code. The default value is |
|
|
The state or province of the storage VM. |
|
|
The locality of the storage VM. |
|
|
The organization of the storage VM. |
|
|
The unit in the organization of the storage VM. |
|
|
The email address of the contact administrator for the storage VM. |
|
|
The cryptographic hashing function for signing the certificate. The default value is |
You provide these values with the security certificate install
command when you install a CA-signed digital certificate for use in authenticating the cluster or storage VM as an SSL server. Only the options that are relevant to account configuration are shown in the following table.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM on which the certificate is to be installed. |
|
|
The certificate type:
|
Configure Active Directory domain controller access
You provide these values with the security login domain-tunnel create
command when you have already configured a SMB server for a data storage VM and you want to configure the storage VM as a gateway or tunnel for Active Directory domain controller access to the cluster.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM for which the SMB server has been configured. |
You provide these values with the vserver active-directory create
command when you have not configured a SMB server and you want to create an storage VM computer account on the Active Directory domain.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM for which you want to create an Active Directory computer account. |
|
|
The NetBIOS name of the computer account. |
|
|
The fully qualified domain name (FQDN). |
|
|
The organizational unit in the domain. The default value is |
Configure LDAP or NIS server access
You provide these values with the vserver services name-service ldap client create
command when you create an LDAP client configuration for the storage VM.
Only the options that are relevant to account configuration are shown in the following table:
Field |
Description |
Your value |
||
---|---|---|---|---|
|
The name of the storage VM for the client configuration. |
|||
|
The name of the client configuration. |
|||
|
A comma-separated list of IP addresses and host names for the LDAP servers to which the client connects. |
|||
|
The schema that the client uses to make LDAP queries. |
|||
|
Whether the client uses Start TLS to encrypt communication with the LDAP server (
|
You provide these values with the vserver services name-service ldap create
command when you associate an LDAP client configuration with the storage VM.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM with which the client configuration is to be associated. |
|
|
The name of the client configuration. |
|
|
Whether the storage VM can use the LDAP client configuration ( |
You provide these values with the vserver services name-service nis-domain create
command when you create an NIS domain configuration on an storage VM.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM on which the domain configuration is to be created. |
|
|
The name of the domain. |
|
|
ONTAP 9.0, 9.1: A comma-separated list of IP addresses for the NIS servers that are used by the domain configuration. |
|
|
A comma-separated list of IP addresses and host names for the NIS servers that are used by the domain configuration. |
You provide these values with the vserver services name-service ns-switch create
command when you specify the look-up order for name service sources.
Field |
Description |
Your value |
---|---|---|
|
The name of the storage VM on which the name service look-up order is to be configured. |
|
|
The name service database:
|
|
|
The order in which to look up name service sources (in a comma-separated list):
|
Configure SAML access
Beginning with ONTAP 9.3, you provide these values with the security saml-sp create
command to configure SAML authentication.
Field |
Description |
Your value |
---|---|---|
|
The FTP address or HTTP address of the Identity Provider (IdP) host from where the IdP metadata can be downloaded. |
|
|
The host name or IP address of the SAML service provider host (ONTAP system). By default, the IP address of the cluster-management LIF is used. |
|
|
The server certificate details of the service provider host (ONTAP system). You can enter either the service provider's certificate issuing certification authority (CA) and the certificate's serial number, or the Server Certificate Common Name. |
|
|
Whether the identity of the IdP metadata server must be validated ( |