State of identity variables in Master Software Image and on first boot

Last Updated : May 06, 2021 |
Prolog information
Metadata
Keywords:
After you install and configure Avaya Enterprise Linux, the Enterprise Linux Installer creates user accounts. The sroot and craft account passwords are disabled with no predefined password, unless EASG is enabled. You should use cust and root accounts to login to the server.
User name
Group
Purpose
Status of Account
sroot
root
Avaya Services root access
Disabled
root
root
Customer root access
Enabled
craft
susers
Avaya Services non-root access
Disabled
cust
susers
Customer non-root access
Enabled

First boot

You will not be able to use the Avaya Service accounts, craft and sroot, to gain access to the server once the server is upgraded to Avaya Enterprise Linux 8.x. The craft and sroot accounts will be controlled via EASG as soon as Experience Portal is installed.
The craft and sroot users are disabled unless EASG is enabled. In this case, the craft and sroot users will use challenge/response authentication.
This applies to both non-OVA and OVA deployments.

First root login

The root and cust users which have default values in the software image, are forced to be updated on first root login. These accounts that are needed to log into a newly created system use pre-defined passwords:
Account
User Name
Password
Non-root access
cust
custpw
Root access
root
rootpw
After you login to the server as root using the default password, Avaya Enterprise Linux will enforce an Avaya First Login Experience which will prompt for a new bootloader, root and cust passwords.
To support headless configuration, root & cust are not forced to be updated on first boot, but are forced to be updated on the first root login.