Fix numerous issues with the Access admin creds not persisted, and adminToken disappearing in certain cases (RTFACT-16046)

[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

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Access Server
Affects Version/s: None
Fix Version/s: 6.0.0

Type: Sub-task Priority: High
Reporter: Uriah Levy Assignee: Uriah Levy
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
duplicates RTFACT-16046 Fix numerous issues with the Access a... Resolved


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.

Generated at Mon Jun 01 20:35:04 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.