Configuring Asg Authentication - Avaya G250 Administration Manual

Note:
You can also upload the authentication file from the gateway for troubleshooting.
Note:
To upload the authentication file, use copy auth-file ftp to upload it to an
FTP server, copy auth-file scp to upload it to an SCP server, copy
auth-file tftp to upload it to a TFTP server, or copy auth-file USB to
upload it to a USB mass storage device. To display the upload status, use show
upload auth-file status.

Configuring ASG authentication

You can perform the following ASG configurations:
Block Avaya Services login access, using no login authentication
●
services-logins. This deactivates all Avaya Services logins, including local craft
password-based authenticated login. To reactivate, use login authentication
services-logins.
Set the time the gateway waits for user response to authentication requests before timing
●
out a connection, using login authentication response-time time, where time
is the time, in seconds, after which the gateway aborts the connection if no response is
received.
For example, to timeout connections if no response arrives within 180 seconds after an
authentication request:
G350-001(super)# login authentication response-time 180
Use no login authentication response-time to return the response time value
to the factory default of 120 seconds. The time value you enter is used for both:
The response time interval between the username prompt and the username entry
●
The response time interval between the challenge prompt and the challenge response
●
Deactivate password authentication and activate ASG authentication of Avaya Services
●
local connections to the Console port. To do this, use no login authentication
local-craft-password. To enable password authentication of Avaya Services local
connections to the Console port, use login authentication
local-craft-password (default).
Managing login permissions
Issue 5 June 2008 57