Security

The Security page allows you to configure security settings for the DXi, including access passwords, LDAP/AD, SSL settings, and the inactivity timeout.

To access the Security page, click the Configuration menu, click the System tab, and then click the Security tab.

The Security page contains the following tabs:

The System Users page allows you to manage access to the DXi for the remote management console (GUI) and the command line interface (CLI) pre-configured accounts.

Note: Click on the Show Password icon () to see the password. For most password entries, after saving entries and leaving the screen , this icon will no longer show the password.

The DXi has the following access levels for logging onto the remote management console or the GUI:

System User Description
Graphical User Interface (GUI)
GUI Administrator Allowed to view and change information on the DXi remote management console.
GUI Monitor Allowed to view information on the DXi remote management console but cannot make changes. The Manage System Users page is view only.
GUI Service This control is disabled by default.
Command Line Interface (CLI)
CLI Administrator (username: cliadmin)

Allowed to view and change information on the DXi CLI.
CLI Viewer (username: cliviewer) Allowed to view information on the DXi CLI  but cannot make changes.
Service Login
SSH/CLI Service (username: ServiceLogin) Allow Secure Shell (SSH) remote access to the ServiceLogin account.

To access the System Users page, from the Security tab, click the System Users tab.

Tasks

Use the System Users page to perform the following tasks:

Note: For better security, do not enable these accounts unless they are needed and then disable them when possible.

Use the GUI password when logging onto the remote management console as an administrator. See Accessing Remote Management.

  1. Under GUI Administrator enter the following information:

    Old Password Enter the old password.
    New Password Enter the new password.
    Confirm New Password Enter the new password again to confirm it.

    Additional Information

    • Disabling the GUI Administrator - You cannot disable this account unless LDAP/AD is enabled. In addition, you must also be logged in to the system as an LDAP/AD user. See LDAP/AD. You can, however, disable this account if you have created an RBAC Admin account.
    • Passwords can be up to 32 characters. Alphanumeric characters and special characters are allowed.
    • Loss of this password will require Quantum service support.
  2. Click Apply.

Use the GUI password when logging onto the remote management console as a monitor. See Accessing Remote Management.

  1. Under GUI Monitor do one of the following steps:

    • Select the Enable account check box to enable the GUI monitor account.
    • Clear the Enable account check box to disable the GUI monitor account.

  2. Enter the following information:

    New Password

    Enter the new password.
    Confirm New Password Enter the new password again to confirm it.

    Additional Information

    Passwords can be up to 32 characters. Alphanumeric characters and special characters are allowed.

  3. Click Apply.

The CLI accounts provide access to the DXi command line interface as an administrator or viewer.

Note: To add another layer of system security most DXi Administrators will want to leave these accounts disabled until they are needed. For more information about using the CLI, see the DXi Command Line Interface (CLI) Guide.

  1. Under CLI Administrator or CLI Viewer, do one of the following steps:

    • Select the Enable account check box to enable the CLI administrator or viewer account.
    • Clear the Enable account check box to disable the CLI administrator or viewer account.

  2. The CLI administrator and view accounts may be configured with Secure Shell (SSH) key-based authentication.

    Add an SSH Public Key

    1. Click Add.

      The Add Public Key page displays.

    2. Enter an SSH Alias for the public key.

      Additional Information

      • An alias can be up to 20 characters.
      • The Alias must be an alphanumeric string (no spaces or special characters).
      • The same alias can be used for different accounts (CLI Administrator and CLI Viewer).

    3. Copy and paste the Public Key generated from a SSH key.

      Additional Information

      • A public key should be in the following form: <key-type> <base64 encoded string>.
      • A public key length can be up to 16kb.

      Sample Public Key Page

    4. Click Apply.

      The "Successfully performed Security action" message appears.

    5. Click OK.

      The new key appears in the CLI Administrator or View Available SSH Public Keys table.

      The Available SSH Public Keys table contains the following information:

      Alias Name of key.
      Fingerprint Short sequence of bytes used to identify a public key.

    Edit an SSH Public Key

    1. Select the check box next to the public key in the Available SSH Public Keys table.

    2. Click Edit.

      The Edit Public Key page displays.

    3. Edit the Alias name.

      Note: The key cannot be modified. To remove a key, see Delete an Alias Name.

    4. Click Apply.

      The "Successfully performed Security action" message appears.

    5. Click OK.

      The updated key appears in the Available SSH Public Keys table.

    Delete an Alias Name

    1. Select the check box next to the public key in the Available SSH Public Keys table.

    2. Click Delete.

      The Delete Public Key page displays.

    3. Click Yes.

      The "Successfully performed Security action" message appears.

    4. Click OK.

      The key is removed in the Available SSH Public Keys table.

  3. In addition to configuring SSH authentication, the CLI Administrator and view accounts may also be configured with password authentication.

    • Select the Allow login with password check box to enable a password on a CLI Administrator or CLI Viewer account.
    • Clear the Allow login with password check box to disable a password on a CLI Administrator or CLI Viewer account.

    Enter the following information:

    New Password Enter the new password.
    Confirm New Password Enter the new password again to confirm it.

    Additional Information

    • Passwords can be up to 32 characters. Alphanumeric characters and special characters are allowed.
    • For accounts enabled with both SSH and password authentication, the system will first attempt SSH authentication . If there are no keys defined or no client key matches, the system will fall back to password authentication.
  4. Click Apply.

Use the GUI password when logging onto the remote management console as a service account. See Accessing Remote Management.

To enable or disable the GUI service account:

  1. Under GUI Service do one of the following steps:

    • Select the Enable account check box to enable the GUI service account.
    • Clear the Enable account check box to disable the GUI service account.

  2. Enter the following information:

    New Password Enter the new password.
    Confirm New Password Enter the new password again to confirm it.

    Additional Information

    Passwords can be up to 32 characters. Alphanumeric characters and special characters are allowed.

  3. Click Apply.

The SSH service account provides SSH remote access to the DXi system.

  1. Under SSH Service, do one of the following steps:

    • Select the Enable account check box to enable SSH service account
    • Clear the Enable account check box to disable the SSH service account

  2. The SSH service account may be configured with Secure Shell (SSH) key-based authentication.

    Add an SSH Public Key

    1. Click Add.

      The Add Public Key page displays.

    2. Enter an SSH Alias for the public key.

      Additional Information

      • An alias can be up to 20 characters.
      • The Alias must be an alphanumeric string (no spaces or special characters).

    3. Enter the Public Key generated from a SSH key.

      Additional Information

      • A public key should be in the following form: <key-type> <base64 encoded string>.
      • A public key length can be up to 16kb.

      Sample Public Key Page

    4. Click Apply.

      The "Successfully performed Security action" message appears.

    5. Click OK.

      The new key appears in the Available SSH Public Keys table.

      The Available SSH Public Keys table contains the following information:

      Alias Name of key.
      Fingerprint Short sequence of bytes used to identify a public key.

    Edit an SSH Public Key

    1. Select the check box next to the public key in the Available SSH Public Keys table.

    2. Click Edit.

      The Edit Public Key page displays.

    3. Edit the Alias name.

      Note: The key cannot be modified. To remove a key, see Delete an Alias Name.

    4. Click Apply.

      The "Successfully performed Security action" message appears.

    5. Click OK.

      The updated key appears in the Available SSH Public Keys table.

    Delete an Alias Name

    1. Select the check box next to the public key in the Available SSH Public Keys table.

    2. Click Delete.

      The Delete Public Key page displays.

    3. Click Yes.

      The "Successfully performed Security action" message appears.

    4. Click OK.

      The key is removed from the Available SSH Public Keys table.

  3. In addition to configuring SSH authentication, the SSH service account may also be configured with password authentication.

    • Select the Allow login with password check box to enable a password on a CLI administrator or CLI viewer account.
    • Clear the Allow login with password check box to disable a password on a CLI administrator or CLI viewer account.

    Enter the following information:

    New Password Enter the new password.
    Confirm New Password Enter the new password again to confirm it.

    Additional Information

    • Passwords can be up to 20 characters. Alphanumeric characters and special characters are allowed.
    • For accounts enabled with both SSH and password authentication, the system will first attempt SSH authentication . If there are no keys defined or no client key matches, the system will fall back to password authentication.
  4. Click Apply.

The Users page allows DXi System Administrators to:

  1. Add new users for accessing the DXi via the remote management console (GUI) and the command line interface (CLI). Specify the users' roles as Administrator or Operator, which will define users' access to the DXi (GUI and CLI).

  2. Create groups with access rights to specific storage servers, shares, and partitions. Assign the users with Administrator and Operator roles to the new groups, to define their access within the system.

Note: Assigning Administrators to groups is recommended for group organization but is not required, as Administrators have rights to view and modify all storage server data, shares, and partitions.

Caution: When you use this page to enable Operators access to specific storage servers, shares, and partitions, your screen views and access to several different screens and tabs in the DXi GUI, and many links available to Administrators will become unavailable. For example, when Operators click on the Map menu option, they will see only the screens in the system where they have access. See the Management Pages section in The Remote Management Console for an interactive map showing not only available screens based on your access rights but clickable links to reach those pages.

To access the Users page, from the Security tab, click the Users tab.

Tasks

Use the Users page to perform the following tasks:

  • Add users in the DXi system, as either Administrators or Operators. See Adding Users and Assigning Roles.
  • Edit an existing user's credentials. See Editing Users.
  • Delete an existing user. See Deleting Users.
  • Create a group, adding users and specifying access to specific shares and partitions. See Adding a Group.
  • Edit an existing group's name, descriptions, modify assigned users and the group's access to specific storage servers, shares, and partitions. See Editing a Group.
  • Delete an existing group. See Deleting a Group.

To add a User and assign credentials and a role:

  1. On the Users screen under Users, click Add.

    2. The Add User screen is displayed.

  2. In the Name box type the name for the new user.

    Note: A User and a Group cannot have the same name.

    Note: Maximum length for the Name field is 31 characters. Valid characters are A-Z, a-z, 0-9, -, _, and . Dashes are not allowed at the beginning of the username. Fully numeric usernames and . or .. are also not allowed.

  3. Click to assign the Role for the new User, either:

    • Operator - The user will have access to specific storage servers, shares or partitions based on the Group(s) to which the user belongs. Operators are also limited in access to some GUI and CLI commands.

    • Administrator - The user will have abscess to all storage data, shares and partitions.

    Note: See Editing a Group.

  4. In the Password box type the new user's password.

  5. In the Confirm Password box retype the password.

    6. The two passwords must be identical.

  6. (Optional) in the Description box type a description of the user. This can include the planned group(s) for access, department or working function for the user.

  7. Click Apply to add the new user in the system.

    The new user is displayed in the Users list.

    Note: To sort the list alphabetically by Users' names or Roles, click on the Name or Role column headings. The list sorts to display alphabetically.

To edit an existing User's assigned credentials:

  1. On the Users screen under Users, click in the row for the user to edit and click Edit.

    2. The Edit User dialog is displayed.

    Note: All fields on this screen are optional. The user's Role cannot be changed on this screen. To change the role, delete the User and add them in the new role. Only one user at a time can be edited. See Deleting Users and Adding Users and Assigning Roles.

  2. In the Name box edit or change the User's name.

    Note: A User and a Group cannot have the same name.

    Additional Information

    • Maximum length for the Name field is 31 characters. Valid characters are A-Z, a-z, 0-9, -, _, and . Dashes are not allowed at the beginning of the username. Fully numeric usernames and . or .. are also not allowed.

    • The User's Role cannot be changed on this screen. To change the role, delete the User and add them in the new role. Only one user at a time can be edited. See Deleting Users and Adding Users and Assigning Roles.

  3. In the Password box edit or change the user's password.

  4. In the Confirm Password box retype the password.

    5. Additional Information

    • The two passwords must be identical.

    • You cannot copy-and-paste the new password from the Password box into the Confirm Password box. It must be retyped.

    Password Requirements

    Passwords must be between 8-64 characters, and must include at least one upper case (A-Z), one lowercase (a-z), one number (0-9), and one special character ( ` ~ ! @ # $ % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < > / ? space ).

    Note: Existing passwords for all users remain valid and are not subject to these requirements.

  5. (Optional) In the Description box edit or change the description of the user. This can include the planned group(s) for access, department or working function for the user. The Description can be up to 255 characters.

  6. Click Apply to save the user changes in the system.

To delete an existing User from the system:

  1. On the Users screen under Users, click in the row for the user to delete and click Delete.

    2. A confirmation message appears.

  2. Click Yes to delete the user.

Adding a Group from the Users screen allows you to create a new group, select an unlimited amount of users from the Selectable Users list, and set their rights to view and work in specific storage servers, shares and partitions.

To create a new group and add users from the Selectable Users list:

  1. On the Users screen under Groups, click Add.

    2. The Add Group dialog is displayed.

  2. In the Name box type a name for the group.

    Note: A Group and a User cannot have the same name.

    Note: Maximum length for the Name field is 31 characters. Valid characters are A-Z, a-z, 0-9, -, _, and . Dashes are not allowed at the beginning of the username. Fully numeric usernames and . or .. are also not allowed.

  3. (Optional) In the Description box type a description of the group. You can note the planned users' data, share, or partition access, department(s) for the group or any other information.

  4. To add Users to the new group, click on the User's name in the list of Selectable Users.

    The user moves to the Selected Users list.

    Note: To search for a user in the list, you can either scroll in the alphabetized list to find the name or type the name in the search box above the list. As you type the name, the list changes to show applicable User names, making it easy to find the desired User.

  5. Repeat the process for additional users to add to the Selected Users list.

To specify Group members' access to specific storage servers, shares and partitions:

  1. Click on the Storage Servers, Shares, or Partitions tab as applicable to find the items where the group will have assigned access.

  2. Click in the box in the row to select each item where the Group will have access.

  3. Click Apply to create the Group in the system.

    4. The new Group is displayed in the Groups list.

    Note: To sort the list alphabetically by Group names, click on the Name column heading. The list sorts to display alphabetically.

Use the Edit Group dialog from the Users screen to modify an existing group's:

  • Name

  • Description

  • Assigned Users

  • Specific access to storage servers, shares and partitions.

To modify an existing group's name, description and selected users:

  1. On the Users screen under Groups, select the row for the group to edit and click Edit.

    2. The Edit Group dialog is displayed.

  2. In the Name box edit or change the group name.

    Note: A Group and a User cannot have the same name.

    Note: Maximum length for the Name field is 31 characters. Valid characters are A-Z, a-z, 0-9, -, _, and . Dashes are not allowed at the beginning of the username. Fully numeric usernames and . or .. are also not allowed.

  3. (Optional) In the Description box edit or type a description of the group. You can note the planned users' data, share, or partition access, department(s) for the group or any other information.

  4. To add Users to the group, click on the User's name in the list of Selectable Users.

    The user's name moves to the Selected Users list.

    Note: To search for a user in the list, you can either scroll in the alphabetized list to find the name or type the name in the search box above the list. As you type the name, the list changes to show applicable User names, making it easy to find the desired User.

  5. Repeat the process for additional users to add to the Selected Users list.

  6. To remove Users from the group, click on the User's name in the list of Selected Users.

    The user's name moves to the Selectable Users list.

  7. Repeat the process for additional users to remove from the Selected Users list.

To modify the Group members' access to specific storage servers and shares:

  1. Click on the Storage Servers, Shares, or Partitions tab as applicable to find the items where the group will have assigned access.

  2. Click in the checked box in each row to select the items where the Group will no longer have access.

    3. Note: To search for an item in the list for each tab, you can either scroll in the alphabetized list to find the item or type the name in the search box above the list. As you type the name, the list changes to show applicable items.

  3. Click Apply to save your changes to the group.

    4. The modified Group is displayed in the Groups list.

To delete an existing Group, which removes the group members' access to specified storage server data, shares and partitions:

  1. On the Users screen under Groups, click in the row for the group to delete and click Delete.

    2. A confirmation message appears.

  2. Click Yes to delete the group in the system.

The LDAP/AD page is used to configure the DXi system to use the LDAPv3 protocol and connect to a remote server for the purpose of authenticating login credentials. The DXi will assign permissions to the login based on the group membership in the LDAP server. Microsoft Active Directory (AD) can be configured to support LDAP and the DXi can then connect to the AD server for the purposes of authenticating login credentials.

LDAP and AD Terms

Common Name (CN)

An attribute that is commonly used to distinguish items at the same (usually top) level in the LDAP hierarchy.

Example

The SysAdmin group would have cn=sysadmin.

Domain Component (DC)

The domain of the directory, which often identifies the organization or company.

Example

Mycompany.com would have a domain of dc=mycompany,dc=com.

Distinguished Name (DN)

A pathway that tells LDAP where information is stored in its directory. LDAP reads the pathway from right to left, with the farthest right components providing the domain of the directory and the farthest left component providing the information for which LDAP is looking.

Organizational Unit (OU)

A component used to organize information into a hierarchical structure. OUs can be used at multiple levels within the LDAP or AD directory, such as to act as a larger Group bucket that then holds individual group OUs.

Tasks

Use the LDAP/AD page to perform the following tasks:

  1. Select the Enable LDAP/AD check box to enable the Connection Settings and Search Strings tables.

  2. Enter the following Connection Settings information:

    Primary Server Domain

    Enter the LDAP/AD domain server.

    Local LDAP Cache

    • The cache will be purged anytime LDAP settings are changed.

    • If LDAP is enabled, the cache can be purged at any time by clicking the Apply button. The cache is purged only if the settings are valid (the LDAP server must be accessible) and saved successfully.

    • If the new LDAP domain server is invalid, user credentials from the previous LDAP server will continue to authenticate from the server cache.
    Alternate Server Domain (Optional) Enter an alternate LDAP/AD domain server
    StartTLS/LDAPS

    Select one of the following:

    • Start TLS - Select to encrypt the connections to the LDAP/AD server. This enables a secure connection over a standard port. Do not enable Start TLS to encrypt connections if the server URL uses a secure protocol (LDAPS).
    • LDAPS - Select if the server URL uses the LDAPS secure protocol.
    Port
    • Start TLS - Default port is 389.
    • LDAPS - Default port is 636.

    Note: Entering a port setting will disable the default port settings.

    Schema

    Specifies the Schema Type in use on the target LDAP server.

    IMPORTANT NOTES:

    Select one of the following:

    • OpenLDAP

    • Active Directory

    • IPA

    Options

    Case Sensitive - Select this box to indicate user names are case sensitive. The box is checked by default for OpenLDAP and IPA schemas. The box is unchecked by default for the Active Directory schema. The state of the box can be changed to override the default behavior. Check with an administrator of the LDAP server for the correct value.

    Test Password Expiration - This check box is available only when schema IPA is specified. The IPA server may allow an expired account to be authenticated. Select this box to perform a test, in addition to authentication, for expiration of the account.
    Password Expiration Attribute

    This field is available only when Test Password Expiration is checked. This is the name of the attribute that will checked for the expiration date/time information. The default value is krbPasswordExpiration.
    Certificate URL

    Enter the URL where the Certificate Authority (CA) certificate in PEM format can be downloaded from.

    Note: As only one or the other can be used to upload a certificate, entries in the Certificate URL field will automatically gray-out (make inactive) the Certificate File field.

    CA Certificate Expiration Alerts

    The following system alerts occur as a certificate approaches expiration:

    • 14 days from expiration - An admin alert is created.
    • 3 days from expiration - If the local GUI Admin account is enabled, an admin alert is created. If the local GUI Admin account is disabled, a service ticket is created.
    • 1 day from expiration - If the local GUI Admin account is enabled, an admin alert is created. If the local GUI Admin account is disabled, the account is enabled and a service ticket is created.

      • See Admin Alerts and Service Tickets.
    Certificate File

    Click Browse to browse to and select the local file to upload to the system.

    Note: As only one or the other can be used to upload a certificate, entries in the Certificate File field will automatically gray-out (make inactive) the Certificate URL field.
    Principal (bind) DN

    Enter the domain name of the principal user. The principal is an account on the LDAP server that can access the authentication hierarchy.

    Example - uid=admin,ou=People,dc=mycompany,dc=com
    Password Enter the password for the principal user.
    Confirm Password Re-enter the password for the principal user.

    3. Password Requirements

    Passwords must be between 8-64 characters, and must include at least one upper case (A-Z), one lowercase (a-z), one number (0-9), and one special character ( ` ~ ! @ # $ % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < > / ? space ).

    Note: Existing passwords for all users remain valid and are not subject to these requirements.

  3. Enter the following Search Strings information:

    User DN

    Enter a distinguished name for retrieving user information.

    Example - dc=mycompany,dc=com
    Monitor Group

    Enter a distinguished name or common name for the monitor users allowed on the DXi system. One group (Monitor or Admin) is required for LDAP/AD configuration.

    Example - cn=user,ou=Group,dc=mycompany,dc=com
    Admin Group

    Enter a distinguished name or common name for the admin users allowed on the DXi system. One group (Monitor or Admin) is required for LDAP/AD configuration.

    Example - cn=sysadmin,ou=Group,dc=mycompany,dc=com
    Access Control Administrator Group Enter a distinguished name or common name for the group that will contain access control administrators. Any members of the group that require access to the DXi must also be added as users on the DXi. See Adding Users and Assigning Roles.
    Access Control Operator Group Enter a distinguished name or common name for the group that will contain access control operators. Any members of the group that require access to the DXi must also be added as users on the DXi. See Adding Users and Assigning Roles.

  4. (Recommended) Test the LDAP/AD settings before applying the settings to the DXi system. See Test LDAP/AD Settings.

    Note: User LDAP/AD settings must be applied before being tested. See step 6 below.

  5. (Recommended) Test LDAP/AD usernames and passwords before applying the LDAP/AD settings to the DXi system. See Test LDAP/AD User.

  6. Click Apply. Changes to LDAP/AD settings forces a log out of the DXi system. Click Yes to continue.

    Note: Clicking the Apply button will purge the LDAP/AD cache of authenticated accounts if the settings are valid.

De-select the Enable LDAP/AD check box to disable LDAP/AD on the DXi system. The LDAP/AD settings remain saved.

Click Test Settings to test the connection settings between the DXi system and LDAP/AD domain server. A successful connection will be indicated by a Success dialog box. A test connection that fails will be indicated by a Failure dialog box containing the reason for the failure.

Successful LDAP/AD Connection

Failed LDAP/AD Connection

Note: User LDAP/AD setting changes must first be applied before being tested.

  1. Click Test User to test the ability of a LDAP/AD user to successfully log into the DXi system. The Test Username and Search Strings dialog box opens.

  2. Enter the following information:

    Username Enter the user name.
    Password Enter the user password.
  3. Click Test.

The SSL/TLS page allows you to enable or disable SSL/TLS on the DXi. You can also install a new SSL certificate to replace the Quantum default SSL/TLS certificate.

To access the SSL/TLS page, on the Security page, click the SSL/TLS tab.

Additional Information

  • If you enable SSL/TLS see Server Authentication Warnings for important information about Web browser settings.

  • SSL/TLS is automatically enabled by default after a fresh installation of system software.

Tasks

  • Use the SSL/TLS page to perform the following tasks:
  • Enable or disable SSL/TLS on the DXi. See Enabling SSL/TLS.

SSL (Secure Sockets Layer)/TLS (Transport Layer Security) is a protocol that provides security and privacy over the Internet by negotiating encryption keys before transmitting data between a client and a server.

To establish a secure connection, the DXi must have an encryption key assigned to it by a Certification Authority in the form of a certificate file, private key file, and pass phrase. After you install these components, you can establish a secure connection using the SSL/TLS protocol. The DXi comes with a Quantum default SSL/TLS certificate.

To enable or disable SSL/TLS:

  1. Under SSL/TLS Properties, select the Enable SSL/TLS option to enable SSL/TLS.

    2. Or select the Disable SSL/TLS option to disable SSL/TLS.

    Note: The default setting is disabled.

  2. Click Apply.

Enabling SSL/TLS with the default Quantum certificate allows you to securely communicate with the DXi Web-based interface using SSL/TLS encryption. However, you may receive a warning from your Web browser and network security scanners stating that the server you are attempting to connect to does not match the server embedded within the certificate.

This is expected behavior because the default certificate can only be used for encryption and not server authentication. Quantum recommends the default Quantum certificate be replaced with your own official certificate specific to your system . You can install your own custom certificate in order to take advantage of server authentication in addition to encrypted communication.

Suppress the server authentication warnings as you would for any site based on the browser you are using. ALWAYS confirm you are on the correct URL before doing so.

You can purchase and install your own custom SSL/TLS certificate in order to take advantage of server authentication in addition to encrypted communication on the DXi.

To install an SSL/TLS certificate:

  1. Under Certificate, click New.

    The Secure Socket Layer (SSL)/Transport Layer Security (TLS) page displays.

  2. In the Certificate File box, type the location and filename of the new SSL/TLS certificate file.

    Or click Browse to browse the system and locate the SSL/TLS certificate file. The SSL/TLS certificate file must be named server.crt.

  3. Click Upload.
  4. Type your SSL/TLS private key and press Enter.

  5. Type your SSL/TLS passphrase and press Enter.

    A Successful Upload page displays stating that the SSL/TLS certificate file has been installed on the system.

  6. Click OK.

    The certificate displays in the Certificate section.

The Data Encryption page allows you to select the type of encryption to use for Replication, OST, and Accent data transfers. Data sent from the media server (OST/Accent) or source system (Replication) to the system can be encrypted using AES (Advanced Encryption Standard) encryption methods.

To access the Data Encryption page, on the Security page, click the Data Encryption tab.

Important Information

  • If TLS with AES 256 is selected, the factory installed certificates are inadequate for security. The factory installed certificates should be considered public domain and are provided only for convenience. You must install new certificates for secure encryption.

  • The system uses the TLS with AES 256 certificate authority as the arbiter of trust. To ensure the security of your data on the system blockpool, you must generate your own private certificate authority.

  • Certificates must contain the following key usage fields / extensions, (replace <<URI>> with the applicable URI)

basicConstraints = CA:FALSE

subjectKeyIdentifier = hash

authorityKeyIdentifier = keyid,issuer:always

keyUsage = critical, nonRepudiation, digitalSignature, keyEncipherment, keyAgreement

extendedKeyUsage = critical, serverAuth, clientAuth

crlDistributionPoints = URI:<<URI>>

subjectAltName=${ENV::BC_SAN}

  • Installing new certificates requires a reboot of the system.

To enable or disable data encryption:

  1. Select an Encryption option in OST and Accent Data Transfer Encryption:

    None Data is not encrypted.
    Default AES 128 OST and Accent data are encrypted using AES 128-bit encryption.
    Default AES 256 OST and Accent are encrypted using AES 256-bit encryption.
    TLS with AES 256

    OST, Accent, and Replication data are encrypted using AES 256-bit encryption with Transport Layer Security (TLS).

    For replication, you must specify encryption settings when configuring the replication or failback targets. See Replication .

  2. If you selected the TLS with AES 256 encryption option, install the required TLS Certificate and key files on the system:

    • Certificate File
    • Private Key File
    • Certificate Authority File
    • Certificate Revocation List (Optional)

    OST Media Server with TLS Encryption

    The certificate and key files installed on the system must match the files on the OST media server. For more information on certificate and key files, see the OST Plug-in Installation Instructions.

    Replication with TLS Encryption

    To successfully use replication with TLS encryption, you must do the following:

    • Configure target system with TLS Encryption.
    • Configure source system with TLS Encryption (system reboot required).
    • Select TLS with AES 256 when configuring the target system. See Adding a Replication Target.

    The source system key and target system key do not need to match, but must meet the following criteria:

    • The target key must be signed by a certificate in the source key.
    • The source key must be signed by a certificate in the target key.

    To install a file, click the Browse button to browse the system and locate the file, and then click Open.

    Caution: Installing certificate files requires a system reboot immediately after the changes are applied. Wait for at least 15 minutes before logging back in.

    Note: You can install new certificate and key files at any time, as long as there are no active network connections between the server and the DXi.

  3. Click Apply. Changes made to the TLS Certificates will require a system reboot and the Save Changes dialog box appears.

    Select one of the following options.

    Option Description
    Defer Reboot

    Defers the system reboot. A Reboot Required alert message will appear in the GUI banner until the system is rebooted.

    Deferring a reboot is only recommended if additional system changes that require a reboot need to be made (Network, Application Environment, Data Encryption changes) or ingest (backup jobs) are currently in progress on the system.

    Note: Once a reboot is in a deferred state, the applied changes cannot be reset.
    Reboot Now

    Starts the system reboot. A system reboot can take up to 15 minutes.
    Cancel No reboot occurs and the Data Encryption page reappears. Changes made to the settings remain but are not applied. Click Reset to reset settings to their original state.

    Additional Information

    • To revert all network settings to the initial state and undo all changes, click the Reset button.
    • To clear all changes without saving them, click Reset. To remove user installed certificate and key files, click Restore Factory Defaults.

The Login Settings page allows Administrators to:

  • Set the system's inactivity timeout in minutes.

  • Enable and disable Multi-Factor Authentication (MFA).

Tasks

Use the controls on the Login Settings page to complete the following tasks:

To access the Login Settings page, on the Security tab, click on the Login Settings tab.

The Inactivity Timeout setting allows you to specify the inactivity timeout for the DXi remote management console. The default timeout is 30 minutes.

When the remote management console is inactive for the time period specified, the user is automatically logged off and must log back on to continue. See Accessing Remote Management.

To specify the inactivity timeout for all system users:

  1. In the Inactivity Timeout box, enter the number of minutes of inactivity before a user is automatically logged off (1–600 minutes).
  2. Click Apply.

GUI Administrators use this feature to enable MFA (Multi-Factor Authentication) feature for RBAC (Role-based Access Control) users. See Adding Users and Assigning Roles for instructions on adding RBAC users.

NOTES

  • For systems configured to use the LDAPv3 protocol and connect to a remote server for the purpose of authenticating login credentials, MFA rules apply to those users. See LDAP/AD.

  • SSH/CLI Service users (username: ServiceLogin) are not required to login with MFA credentials.

  • Downloading an authenticator program is the suggested method of working with MFA.

To enable the system to use MFA:

  1. Under OTP (One-time Password), check the Enable Multi-Factor Authentication box.

    Note: NTP must be enabled to enable the Time-based One-time password and enable MFA. See Date & Time.

  2. Click Apply.

    All users created on the Users page will need to set up and use MFA. See Set Up Multi-Factor Authentication.

After enabling MFA, when users are added in the system using the System > Security > Users page, at first login, they will need to set up their MFA:

  1. At the Login screen, type your Username and Password, and then click on Login.

    Password Requirements

    Passwords must be between 8-64 characters, and must include at least one upper case (A-Z), one lowercase (a-z), one number (0-9), and one special character ( ` ~ ! @ # $ % ^ & * ( ) - _ = + [ ] { } \ | ; : ' " , . < > / ? space ).

    Note: Existing passwords for all users remain valid and are not subject to these requirements.

  2. The Login screen changes to display a QR code screen similar to the following image:

  3. Using your authenticator application, select your account for company use and either:

    • Scan the QR code.

    • Copy and paste or type the 32-character Shared Secret Code into your authenticator application.

    Your authenticator application generates a 6-digit One-time password code.

  4. On the Login screen still displaying the QR code, type the One-time password code in the Authentication code box, and then click Apply.

    You are logged on to your system with your MFA code and the Home screen is displayed.

For subsequent logins after completing your MFA setup:

  1. At the Login screen, type your Username and Password, and then click on Login.

    The Login screen changes to display an Authentication code box.

  2. Using your Microsoft Authenticator application, select your company account and type the 6-digit One-time password code in the Login screen Authentication code box, and then click Apply.

    You are logged on to your system with your MFA code and the Home screen is displayed. This is now your regular login process.

Caution: Disabling MFA deletes all secret keys created for RBAC-setup users. When MFA is re-enabled, users will need to re-authenticate using the steps in Security and Security

To disable MFA for all system users:

  1. Under OTP (One-time Password), un-check the Enable Multi-Factor Authentication box.

    A confirmation message displays, reminding you that disabling MFA for all users and the secret authentication key for each will be deleted from the system.

  2. Click Yes to continue or No if you need to leave MFA in place for the system.

If, for example, a user loses their phone containing the authenticator application and their account information, the GUI Administrator can delete the user's secret key. Under TOTP User Settings, click in the Username box under Delete user's secret key and enter the user's Username to remove the user's Shared Secret Code from the system.

Note: The terms Secret Key and Shared Secret Code refer to the same character string. The terms will be merged in a future release.

To remove a user's secret key:

  1. Under TOTP User Settings, type the user's Username in the Username box.

  2. Click on Delete secret key.

    A confirmation message is displayed.

  3. Click on Yes to confirm the deletion.

    Note: A system message on the screen confirms that the user's secret key has been deleted. At the user's next login, they must repeat the processes in Set Up Multi-Factor Authentication and Set Up Multi-Factor Authentication. They may also need to add their company account in authenticator.

The Security Notice page allows you to specify a message that will appear to all users when logging on to the remote management console or the CLI (command line interface).

If a security notice message has been specified, the user must accept the message in order to begin using the system. If no security notice has been specified, the user can use the system immediately after logging on.

To access the Security Notice page, on the Security page, click Security Notice.

To add or update a security notice message, enter the message in the box and click Apply.