Enabling password expiry policy after update to Exasol 6.1 may lead to users being locked immediately
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7729 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0 |
| Fix Versions | Exasol 6.1.3 |
| Resolution Date | 2019-04-18 |
Problem description
New columns were added in Exasol 6.1.0 to EXA_DBA_USERS table for the Password Expiry Policy feature. Unfortunately, these columns are not correctly initialized during the upgrade process from 6.0.
The PASSWORD_STATE_CHANGED column should show the timestamp when the password state had changed. It should be set to the current timestamp at the time of the upgrade to 6.1. Instead it is being set to NULL or 1-JAN-1970. This may lead to users being blocked when Password Expiry Policy is enabled.
Workaround
DBA can reset passwords for all users to the same passwords as before using the hash value. This will cause PASSWORD_STATE to change to "VALID" and PASSWORD_STATE_CHANGED will contain the timestamp when the password was reset.
ALTER USER U1 IDENTIFIED BY HASH VALUE "91A8E4DB4DA4743A55EC5FFFED611EE5F649BD0E87D87AFD90E7DFD5";
