Administration Guides

Appliance Security, Authentication & Hardening

Home


Overview

This section covers login and authentication options for Golden Copy administrators.  

User Roles

  1. Golden Copy has an administrator role for cluster configuration and cluster operations (up, down, upgrades). The user is "ecaadmin".
  2. If additional administrator users are created they are only able to configure copies and run copy jobs.  Cluster operations are blocked.
  3. This guide explains how to create new users, groups and create roles by assigning CLI commands to a group. 

Authentication & Login

Overview

The Golden Copy vm supports OS login options and Application authentication options to allow configuration changes.  The ecaadmin user is the appliance administrator that is used for managing the software operating environment changes to system configuration files and can also be used to start up and shutdown the application.  

The options for OS login include locally created users and groups in the OS to control who can access CLI or Active Directory OS login can also be used.

Read Me First

  1. This feature is designed for 2 use cases
    1. Creating new administrators with all CLI command access with either local os login or remote AD login
    2. Creating a role for operators to monitor copy job progress and view stats but will unable to change configuration.
    3. Creating additional administrators
    4. NOTE:  ecactl commands are restricted to the ecaadmin user that is the only appliance administrator

How to Enable Administrator RBAC for local OS Users or AD Users (Mandatory)

  1. Activate additional administrators with this command. Without this command no admin users will be allowed to run any commands other than the builtin ecaadmin appliance administrator.  The builtin group for administrators is called ecactl.
    1. searchctl settings groups add --name ecactl --cmd '*'


How to Configure Active Directory OS Login for Application Users

  1. This requires joining the appliance to Active Directory.
    1. login as ecaadmin over ssh
    2. sudo -s (enter ecaadmin password)
    3. Type YAST
    4. Navigate to Windows Domain Membership

    5.  Enter your AD domain and select options as per the screenshot below

    6. Enter domain admin or an account that allows computers to be joined to the domain.
    7. Once joined successfully, exit YAST using tab to select quit.   
    8. Test ssh login with AD
    9. example login syntax for an AD domain called ad2.test with user demo1.  NOTE: the double slash is required to escape slash character
      1. Linux ssh client login
        1. ssh ad2.test\\demo1@x.x.x.x    OR
        2. ssh demo1@ad2.test@x.x.x.x  
      2. Putty windows tool
        1. User name: demo1@ad2.test
    10. This allows OS login but blocks application CLI commands until the AD user is added to a role.
    11. Proceed to How to Configure Additional AD appliance Administrators .


How to Configure Additional AD User Appliance Administrators

  1. Follow these steps to add an AD user to the builtin ecactl local group that provides access to all searchctl commands. 
  2. NOTE:  You must follow the steps to join the appliance to AD before using these procedures.
  3. Login as ecaadmin user 
  4. sudo /usr/sbin/usermod -a -G ecactl AD02\\xxxx   (AD02 is the domain name in upper case and xxxx is the user name in AD to add to the group, NOTE the double slash is required as an escape character)
  5. Logout and test the user access
  6. example login syntax for an AD domain called ad2.test with user demo1. NOTE: the double slash is required to escape slash character
    1. Linux ssh client login
      1. ssh ad2.test\\demo1@x.x.x.x OR
      2. ssh demo1@ad2.test@x.x.x.x
    2. Putty windows tool
      1. User name: demo1@ad2.test​
  7. test CLI commands


How to Configure Additional Local OS Appliance Administrators 

  1. This command will add a new OS local user that will be added to the local OS group ecactl providing access to full appliance cli.   
  2. Ssh ecaadmin@x.x.x.x
  3. searchctl settings users add --name NAME   (you will be prompted to enter the ecaadmin appliance administrator password)
  4. Set the password for the new user
    1. sudo passwd NAME  (where the user name is entered, you will be prompted to enter the eccaadmin user password, then you will be prompted to set the user password)
  5. or searchctl settings users remove --name NAME    (you will be prompted to confirm)
  6. This new user will be able to login and run all commands required to manage the appliance, the user is added to the builtin administrator group called ecactl. NOTE:  activation of all commands must be completed to enable commands.
    1. To view the users in this group cat /etc/group
  7. Login over ssh to test CLI commands

How to create a New RBAC Operator Role for Monitoring Copy Jobs and Stats

  1. Use this command to create a new group role to assign CLI commands to create a user role that defines an Operator role.  This user will be able to monitor copy jobs and statistics on folder configurations.   
  2. ssh to the appliance as ecaadmin
  3. sudo /usr/sbin/groupadd operator
    1. (note: do not use spaces or special characters, when prompted for a password enter the ecaadmin password)
  4. Add the new Group to the appliance with operator role commands
    1. searchctl settings groups add --name operator --cmd  'searchctl archivedfolders list' 'search jobs *' 'searchctl archivedfolders stats *'  
  5. Add an AD user to the new operator group (NOTE:  double slash is required to escape the \ character, use this AD syntax when adding the user)
    1. sudo /usr/sbin/usermod -a -G operator AD02\\demo1 
  6. (optional) How to remove a user from a group (note:  double slash to escape the \ character is required for AD users)
    1. sudo gpasswd -d AD02\\demo1 ecactl
  7. example login syntax for an AD domain called ad2.test with user demo1.  NOTE: the double slash is required to escape slash character
    1. Linux ssh client login
      1. ssh ad2.test\\demo1@x.x.x.x    OR
      2. ssh demo1@ad2.test@x.x.x.x 
    2. Putty windows tool
      1. User name: demo1@ad2.test
  8. Test CLI commands


How to Assign CLI commands to a Role

  1. Overview
    1. The commands below allow creation of customer user roles based on a local OS group that can contain local users or AD users.   The CLI commands can be assigned to the group.   A default group is created named ecactl that is reserved for appliance administration only.   New groups can be created using the steps above to create additional roles,  the Operator role is defined in this guide.
  2. Usage to add and remove CLI commands from a group
    1. searchctl settings groups add --name <group name> --cmd COMMANDS [COMMANDS ...]
    2. searchctl settings groups remove --name <group name> --cmd COMMANDS [COMMANDS ...]
  3. Examples of adding CLI commands to an existing group
    1. Giving access to cli commands as an administrator and all subcommands.
      1. searchctl settings groups add --name ecactl --cmd '*'
    2. Giving access to only searchctl archivedfolders list
      1. searchctl settings groups add --name DemoGr1 --cmd 'searchctl archivedfolders list'
    3. To add multiple commands at once use a space between each command
      1. searchctl settings groups add --name DemoGr1 --cmd 'searchctl archivedfolders *' 'searchctl jobs *' 

How to Create a Custom Role

  1. Overview
    1. This example will create a new role with a group called role1 and assumes AD users are used, in this example the user is AD02\demo1 user in the domain called AD02.  The prerequisite requires the appliance is joined to Active Directory following steps in this guide.
    2. This role will provide monitoring and configuration commands to add or delete or modify folder configurations and start archive copy jobs
  2. Login as ecaadmin user over ssh
  3. Create the group
    1. sudo /usr/sbin/groupadd role1 
  4. Add a user to the group 
    1. sudo /usr/sbin/usermod -a -G operator AD02\\demo1 
  5. Add CLI commands to the group called role1
    1. searchctl settings groups add --name role1 --cmd 'searchctl archivedfolders *' 'searchctl jobs *' 'searchctl archivedfolders stats *'
  6. Done


Managing Access to CLI, WebUI 

How to Access the command line:

  1. ssh to the appliance with a local user account.
    1. The default user is: "ecaadmin", and the default password is: "3y3gl4ss"
    2. example login syntax for an AD domain called ad2.test with user demo1.  NOTE: the double slash is required to escape slash character
      1. Linux ssh client login
        1. ssh ad2.test\\demo1@x.x.x.x    OR
        2. ssh demo1@ad2.test@x.x.x.x 
      2. Putty windows tool
        1. User name: demo1@ad2.test
    3. done

How to Access the WebUI:

  1. https://x.x.x.x (this will present the login page and login with user@domain name and password. NOTE: The user must be added as a local admin first see below) .

Local OS administration and application cluster operations

  1. cluster CLI commands, webUI and upgrade administrator user is "ecaadmin".
  2. SSH login or webUI login.
  3. Configuration and appliance cluster operations.
  4. OS configuration changes requires sudo -s to become root user and this is granted to the ecaadmin appliance administrator only.

How to add new local admin with Access to the WebUI and CLI

  1. Create new local OS administrator with the command command in this section.  This will add the user to the CLI admin role.
  2. This command will add the user to the webUI.
    1. searchctl settings admins add --name <OS user name> --local​​ 
  3. Then set the password for the webUI login
    1. Installation requires the WebUI password to be set. To reset or change this password follow these steps:
    2. Login to node 1 over ssh as ecaadmin user and run the command below
    3. NOTE: Enter the password after the user name
    4. ecactl cluster exec "htpasswd -b /opt/superna/eca/conf/nginx/.htpasswd <user name>  password"
  4. done. The new password is active immediately on all nodes.

How to Add AD Users with Access to the WebUI:

  1. Active Directory users can only access the WebUI, no CLI access will be granted.
    1. The important thing to note is that login will be proxied through to the isilon authentication provider.  This means the user you're attempting to give access must have  access to at least one SMB share on your isilon to test the password.  TCP Port 445 must be open from node 1 to the Isilon
  2. searchctl settings admins add --name <AD user name> (NOTE: syntax is user@domain name) 

How to Configure password policies for local users and ban failed login attempts

The all product steps can be followed here for password complexity and life time policies as well as ban failed login attempts

Operations Guide - All products Hardening Guide





© Superna LLC