Skip to main content

​
Recover Access During an SSO Outage

Collate cannot run Basic Authentication and single sign-on (SSO) at the same time. During an SSO outage, a self-managed or Bring Your Own Cloud (BYOC) operator can temporarily switch the server to Basic Authentication. Fully managed Collate customers must contact Collate Support because only Collate can change the server authentication configuration.
Prepare and test a Basic Authentication administrator account before an outage. Switching providers does not create a usable password for an existing SSO-only account. Changing the provider also invalidates sessions created by the previous provider, and restarting or rolling out the Collate server can briefly interrupt access.
For a self-managed or BYOC deployment:
  1. Confirm that you have deployment access and a tested Basic Authentication administrator credential.
  2. Record the current SSO provider and configuration so you can restore them.
  3. Set authenticationConfiguration.provider to basic. If the configuration uses environment variables, set AUTHENTICATION_PROVIDER=basic.
  4. Restart the Collate server or roll out all Collate server pods so every instance uses the same provider.
  5. Open a private browser session and sign in with the Basic Authentication administrator account.
  6. Restore service or correct the SSO configuration.
  7. Set authenticationConfiguration.provider back to the original SSO provider, restart or roll out every Collate server instance, and verify SSO sign-in.
After you restore SSO, users must sign in again because sessions issued by Basic Authentication are no longer valid.