Fix numerous issues with the Access admin creds not persisted, and adminToken disappearing in certain cases
[RTFACT-16045] Access won't swap old admin creds with new ones on a secondary node during upgrade Created: 06/Mar/18 Updated: 22/Apr/18 Resolved: 22/Mar/18
|Project:||Artifactory Binary Repository|
|Reporter:||Uriah Levy||Assignee:||Uriah Levy|
|Sprint:||Leap 29, Leap 30, Leap 31|
Upgrading from a version below 5.6.0 to 5.6.0 and above requires changing the old access admin credentials with the new ones. On an upgrade scenario, the primary is upgraded first which results in the new access admin being created. When the secondaries start up it's already too late for them to know that they need to replace their client creds due to the fact that the primary already replaced them. The check that depends on the new user's existence in the DB is faulty, and should be changed.