login

system login
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

User login

system login aaa
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

AAA options

system login aaa accounting <id>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Accounting list name

Reference:

system aaa list <id>

system login aaa authentication <id>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Authentication list name

Reference:

system aaa list <id>

AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

System login banners

AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • id –

    Display a message after login

    Example: “Welcome to OSDx!”

AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • id –

    Display a message before login

    Example: “Warning: do not use this system without proper permissions.”

system login idle-timeout <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Timeout interval in seconds

Values:

  • u32 – Disabled (infinite timeout timer) (0)

  • u32 – Seconds (1-65535)

system login max-auth-tries <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Maximum number of authentication attempts allowed per connection

Values:

  • u32 – Number of attempts (1-65535)

system login max-sessions <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • u32 – Maximum login sessions per user

system login password-prompt-delay <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • u32 – Delay of password request in seconds when authentication attempt fails

system login role <txt>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

User role

Values:

  • txt – Role name (1-32)

Instances:

Multiple

Required:

system login role <txt> authentication
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Authentication for role members

system login role <txt> authentication public-key <id>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • id –

    Public key attached to this role

    The key-based authentication involves two files: a public key and a private key. The first one is used for encrypting communications with a client that presumably owns the private key. As the private key should be owned only by a group or an individual, communications are always secure and the identity of the peers is always known. This is the so-called asymmetric encryption.

Instances:

Multiple

system login role <txt> level <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Role privilege level

Values:

  • u32 – Privilege level (0-15)

system login unlock-time <u32>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Time until an account that has hit the maximum number of athentication attemps is unlocked

Values:

  • u32 – Time in seconds (0-65535)

system login user <txt>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

User account information

Values:

  • txt – User name (1-32)

Instances:

Multiple

Required:

system login user <txt> authentication
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE

Authentication password

Required:

system login user <txt> authentication encrypted-password <txt>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • txt – Encrypted password for this user

system login user <txt> authentication public-key <id>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • id –

    Public key attached to this user

    The key-based authentication involves two files: a public key and a private key. The first one is used for encrypting communications with a client that presumably owns the private key. As the private key should be owned only by a group or an individual, communications are always secure and the identity of the peers is always known. This is the so-called asymmetric encryption.

Instances:

Multiple

system login user <txt> role <id>
AresC640 Atlas840 M10-Smart M2 RS420 RXL15000 SDE
Values:

  • id – User role