CMS Supervisor ask pw reset at the login after Backup/Restore

[takakoharada]

Hi All,

Does anyone know that the product behavior below is working as designed?
Regardless of CMS version, either R15, or 16 or earlier release,

1. Conduct Maintenance Backup on CMS data
2. Delete the intended user account from CMS menu
-Ensure that users entry is removed from users home directory, /etc/passwd, and etc/shadow directory
3. Perform Maintenance Menu --> Restore data (check CMS System Admin Data only)
4. Ensure that user home directory, and user data entry in /etc/passwd, and /etc/shadow are restored properly
5. Then, starts CMS Supervisor and tries to login using the deleted account in step 2.
At that time, user is asked to reset the password. Also, if CMS maintenance backup /resore is performed after a new user account was created, that new user was also asked to reset his or her password.
Is this behavior normal expected one, although not defined in the CMS document, as far as I am concerned.
Thank you in advance, Takako Harada - Avaya Japan Ltd

[dsusman]

This is expected when password expiration is set. It also depends on how the customer might reconfigure the login/authentication settings.

[kamra]

Harada San,

This is an expected behaviour, as mentioned by dsusman as well. However, my reasons for concurring are different.

Scenario 1: When you delete a CMS user id say <nippon> completely. That user id is not only deleted from CMS database, but also from the /etc/passwd and /etc/shadow files at the OS level. So when you delete the user is <nippon> after taking a full maintenance backup and thereafter restore the data with system admin data option only, you will have the CMS user id <nippon> contained in the backup data that will get restored and the cms user id <nippon> will get restored along with in the CMS db, but at the OS level the entery with password etc. in /etc/shadow and /etc/passwds file will not be there. So when after restoration of just the maintenance data in CMS, when you login using the <nippon> id through CMS supervisor, it tries to log you in the CMS shell but asks for password to be set as the password entries are not there in /etc/passwd and /etc/shadow files.

Scenario 2: When you create a new CMS user after taking the full maintenance backup and then restore it. The entries for that user may not be there in the CMS db, but they are there at the OS level. Since the CMS application creates the new user ids in such a fashion that the users are asked to set the password on the next login attempt, the OS asks for the password to be set. However, I've not tried, so I'm not sure that <nippon> user in this case will be able to access the CMS application properly as its information in not there in the CMS db.

The above explanation could be refined further though..but crudely this is how it works.

Saurabh Kamra