Skip to main content

Update Okta SSO credentials

If your team signs in to Assembled with Okta single sign-on (OIDC), use these steps to replace the client secret Assembled uses. You create the new secret in Okta, and our Support team updates it in Assembled.

If you're here because of the November 13, 2026 security incident: We're asking customers to replace the credentials for every integration connected to Assembled, including the Okta client secret used for sign-in. If your team signs in with SAML instead, there's nothing to replace; see Integrations that don't need new credentials. For more about the incident, see November 13, 2026 security incident.

Who does this

  • An Okta admin who can manage the Assembled app in your Okta account.
  • Someone on your team who can sign in to Assembled with Okta to test the change.

Before you start

  • Check that your team signs in with Okta OIDC, not SAML.
  • Make sure you can share the new secret securely through 1Password. Support will tell you who to share it with.

Steps

  1. In Okta, open the Assembled app and generate a new client secret. Keep the current secret active until Support confirms the update, so your team can keep signing in.
  2. Contact Support and tell us you've created a new Okta client secret. Share the new secret with us through 1Password. Don't paste it into an email, chat or ticket.
  3. We'll update your Okta configuration in Assembled and let you know when it's done.
  4. Sign in to Assembled with Okta in a new browser window to confirm sign-in works.
  5. Once sign-in works, deactivate the old client secret in Okta.

If a step doesn't match what you see, or you can't finish it, contact Support. We're working through these with customers individually and will help you finish.

How to confirm it's working

  • A new Okta sign-in to Assembled succeeds after Support confirms the update.
  • After you deactivate the old secret, sign-in still works.

When you'll see data

Sign-in changes take effect as soon as Support confirms the update. There's no data to sync.

Restoring missed data

Okta sign-in doesn't sync data, so there's nothing to restore. If anyone on your team can't sign in, contact Support.

Things to watch for

  • Keep the old secret active until we confirm. Deactivating it first locks your team out of Okta sign-in.
  • Share the secret only through 1Password. Don't send it in an email, chat or ticket.
  • Test sign-in before you deactivate the old secret.

Need help?

If something doesn't look right, contact our Support team and include any error text you see when signing in. For more about Okta sign-in, see Okta single sign-on.

Still have questions?