Authentication User Types - AWS Elemental Server

This is version 2.16 of the AWS Elemental Server documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor File and AWS Elemental Server Documentation.

Authentication User Types

This table describes the types of users available with authentication.

User type How created Log-in username Log-in password Use
Default, remote terminal user Built-in Customer-created at install. Default, or as changed by an administrator. Users manually enter this information at these times:
  • When logging in to a remote terminal session for the node.

  • When PAM is enabled and it's the first time that any users access the node after authentication is enabled.

Admin REST API user An administrator enables local authentication on the node when they create the administrator user in the command line. Customer-created.

The username must not be the name of a real person.

Customer-created. The administrator API user is used at these times:
  • The person configuring authentication uses the admin API user information the first time that they access a node's web interface after local authentication is enabled.

    Typically, this is the only time that a user manually uses this user information.

People and third-party clients An administrator user creates these users either through the node's web interface (for local authentication) or through an LDAP server (for PAM authentication). Customer-created. Customer-created.

Users manually enter their log-in credentials when accessing the node through the web interface or REST API.

With local authentication. If a person has access to multiple nodes, you must create a user for them in each node.