Automatic Logout of CLI Sessions
Security administrators can configure an automatic logout of certain user accounts. Limiting the number of
minutes that an interactive CLI session can be in use reduces the consumption of system-wide resources. It
also prevents a user from potentially accessing a user account in a terminal window which is left idle. All
authentication methods described in this section support both the idle session timeout technique and the
absolute session timeout technique.
Most privileged accounts do not require an indefinite login timeout limit.
Configuring the session timeout is strongly recommended for all privileged accounts.
Important
The idle timeout and session timeout fields in the
show tacacs summary
and
show tacacs session id
commands
allow administrators to configure an automatic logout of certain accounts.
Session Timeout
: allows a security administrator to specify the maximum amount of minutes that a user can
be logged in to a session before the session is automatically disconnected.
Idle Timeout
: allows a security administrator to specify the maximum amount of minutes that a session can
remain in an idle state before the session is automatically disconnected.
The session timeout and idle timeout fields are not exclusive. If both are specified, then the idle timeout
should always be lower than the session timeout since a lower session timeout will always be reached
first.
Important
For additional information on configuring the maximum number of minutes that an interactive CLI session
can be in use, see the
idle-sessions threshold
command and the
clear tacacs sessions
CLI command in the
CLI Reference
and the
show tacacs summary
and
show tacacs session id
in the
Statistics and Counter
Reference
.
Configuring SSH Options
SSHv2 RSA is the only version of SSH supported under StarOS. Keywords previously supported for SSHv1
RSA and SSHv2 DSA have been removed from or concealed within the StarOS CLI.
A keyword that was supported in a previous release may be concealed in subsequent releases. StarOS
continues to parse concealed keywords in existing scripts and configuration files created in a previous
release. But the concealed keyword no longer appears in the command syntax for use in new scripts or
configuration files. Entering a question mark (?) will not display a concealed keyword as part of the Help
text. Removed keywords generate an error message when parsed.
Important
Version 1 of the SSH protocol is now obsolete due to security vulnerabilities. The
v1-rsa
keyword has been
removed for the Context Configuration mode
ssh
command. Running a script or configuration that uses the
ASR 5500 System Administration Guide, StarOS Release 21.5
14
Getting Started
Automatic Logout of CLI Sessions