Skip to content

Troubleshooting

Client credentials are exposed

Contain an exposed API client secret or exposed Login client tokens, and confirm revocation with the issuer before you rely on it.

Removing local copies does not invalidate exposed credentials. Only the issuer can confirm that a secret or token no longer works.

Condition

A client secret, an access token, or a refresh token appears in source control, a log, a published artifact, or another place outside its storage.

Solutions

An API client secret is exposed

An API client secret authorizes app-only tokens until support disables the client. The developer API offers secret retrieval and no self-service secret rotation. A reveal of the secret does not generate a different one.

Warning: Never send the secret itself to support. Deletion of a file from Git does not remove the secret from the history. Local token deletion does not invalidate bearer tokens that the issuer already issued.

  1. Stop using the secret.
  2. Stop distributing the secret.
  3. Remove the secret from configuration, logs, and published artifacts.
  4. Send the public client ID and the exposure time to Remilia support.
  5. Ask support to disable the compromised client and replace its credentials.
  6. Ask support about the remaining lifetime and the revocation of issued tokens.
  7. If the replacement needs another API client, register that client.
  8. Wait for approval of the replacement client.
  9. Store the replacement secret in server configuration or an operating system credential store.
  10. Request a fresh app-only token.
  11. Verify a scoped read with the fresh token.
  12. Retire the compromised client in the developer portal.
  13. Confirm the outcome with support.

This procedure does not promise instant revocation. Keep the affected integration disabled until support confirms the status of the compromised client.

Login client tokens are exposed

A Login client has no client secret. Its exposed access tokens and refresh tokens stay valid until they expire or the issuer revokes them.

  1. Clear the local sessions of your app.
  2. Stop distributing the exposed values.
  3. Revoke the exposed tokens as Logout and revocation describes.
  4. If you cannot confirm the revocation, send the public client ID and the exposure time to Remilia support.