How to remove all legacy API tokens in Operations Center

Issue

Legacy API tokens do not get removed in the Client controllers or Managed controllers.

Environment

Resolution

After upgrading Operations Center (OC), Managed controllers (MC) or Client controllers (CC) to 2.129+ and removing all the previous API tokens in either MCs and/or CCs following Security Hardening: New API token system in Jenkins 2.129+, the legacy API tokens appears again.

The Legacy API token clean up must be performed firstly in Operations Center as there is an users synchronization between OC and CCs/MCs which will overwrite what was performed at CC/MC level. After the Legacy API token clean up at OC level, you might want not to wait for the synchronization to happen and perform the clean up at CC at MC as well.

Have more questions?

0 Comments

Please sign in to leave a comment.