Changing maximum expiration days for user passwordsBy default, the passwords that are associated with all usernames created using the XOS CLI expire after 30 days. Some administrators don't want user password to expire. It is possible (but not recommended) to avoid the expiration of user passwords by using the Linux chage command.

However, if an administrator uses lowercase m (minimum days between password changes) instead of uppercase M (maximum days between password changes), future logins are blocked. If this happens, the messages below appear and the login is prevented.

When changing user maximum expiration days, instead of entering an upper case 'M', the system administrator enterd a lower case 'm' (which is minimum expiration days).

Example:

1. A user was created with maximum expiration of 1 day (by default it is of 30 days)

2. The administrator wants to eliminate the maximum expiration requirement using chage. But, enters a lower case 'm' instead of an upper case 'M'.


The output from the command shows that the minimum expiration days parameter was changed (to 9999) and the password will still expire in 1 day.

1. If the user is the admin:

   a) Connect with root user through console and/or ssh, and change the password restriction parameters:

   b) Open a new SSH session and login using admin account as before

   Note: If the root password is not known, follow the instructions listed in the "Recovering from an Expired CPM Root Interval Session" in the XOS Configuration Guide.

2. If the user is other than admin and/or root:

    a) Log in as user admin user and then switch to Linux using the root login.


    b) Open a new SSH session and log in using the user1 account.


After the changes, the user (user1 and admin) should look like below:


If you still have problems logging in, contact Crossbeam Support.

Workaround

N/A