Go to developer

Troubleshoot Popup & Redirect

Popup blockers, closed popups, redirect_uri exact match, state mismatches.

On this page

OAuth redirect_uri uses exact string match. Partner returnUrl uses origin matching — do not confuse them.

Clicking login does nothing or the browser blocks the popup.

  1. Popup blocker
  2. Not triggered from a user gesture
  3. Browser settings
  • Reproduce with blockers disabled.
  • Check KeyraOAuthError code.
  • Use direct gesture.
  • Fall back to redirect.

Related errors: popup_blocked

Related SDK: verifyWithPopup(), verifyWithRedirect()

Related guides: Popup flow

OAuth redirect never returns

Symptom

User leaves for KEYRA and does not return to your callback.

Most likely causes

  1. Wrong redirect_uri
  2. User abandoned
  3. Callback route misconfigured

How to diagnose

  • Watch network for invalid_redirect_uri on start.
  • Confirm callback path is deployed.

How to fix

  • Fix redirect registration.
  • Handle cancel/timeout in UX.

Related errors: invalid_redirect_uri, callback_state_missing

Related SDK: verifyWithRedirect(), handleRedirectCallback()

Related API: POST /oauth/authorize/init, POST /verify/start

Related guides: Redirect flow

redirect_uri is rejected

Symptom

Start fails with invalid_redirect_uri.

Most likely causes

  1. Exact-match failure (slash, scheme, host, port, path)

How to diagnose

  • No normalization — trailing slash matters.
  • Token exchange must reuse the same URI.

How to fix

  • Register and send identical strings.

Related errors: invalid_redirect_uri

Related SDK: createKeyraAuth(), createVerification()

Related API: POST /oauth/authorize/init, POST /oauth/token

Related guides: Redirect flow