What causes redirect_uri_mismatch?

The redirect_uri sent in the authorization request does not exactly match any URI registered in the OAuth provider dashboard. The match is case-sensitive and must include the exact protocol, domain, port, and path.

Why does trailing slash matter in redirect_uri?

OAuth providers match redirect URIs exactly. https://yourapp.com/callback and https://yourapp.com/callback/ are different URIs. Remove or add the trailing slash consistently in both your app and the provider dashboard.

OAuth Error

redirect_uri_mismatch

Last updated: April 2026

OAuth Error Response

error: redirect_uri_mismatch error_description: The redirect_uri does not match any registered redirect_uris.

The redirect_uri your app sent in the authorization request does not exactly match any URI registered in your OAuth provider's dashboard. The match is case-sensitive and includes the full URI: protocol, domain, port, and path.

Diagnose OAuth errors with OAuthFixer →

Fix — match the URI exactly

The redirect_uri in your authorization request must exactly match one of the registered URIs in the provider dashboard. Check for:

# Common mismatches:

# 1. Trailing slash
https://yourapp.com/callback    # registered
https://yourapp.com/callback/   # sent — mismatch

# 2. HTTP vs HTTPS
https://yourapp.com/callback    # registered
http://yourapp.com/callback     # sent — mismatch

# 3. Port mismatch (localhost)
http://localhost:3000/callback  # registered
http://localhost:3001/callback  # sent — mismatch

# 4. Path case
https://yourapp.com/Callback    # registered
https://yourapp.com/callback    # sent — mismatch

Auth0 fix

# Auth0 Dashboard → Applications → Your App → Settings
# Add the exact URI to "Allowed Callback URLs"
# Multiple URIs separated by commas:
https://yourapp.com/callback, http://localhost:3000/callback

Okta fix

# Okta Admin → Applications → Your App → General
# Add to "Sign-in redirect URIs"
https://yourapp.com/callback
http://localhost:3000/callback

Google OAuth fix

# Google Cloud Console → APIs & Services → Credentials
# Click your OAuth 2.0 Client → Edit
# Add to "Authorized redirect URIs":
https://yourapp.com/callback

AWS Cognito fix

# AWS Console → Cognito → User Pools → Your Pool
# App clients → Your client → Edit
# Add to "Callback URLs":
https://yourapp.com/callback

Microsoft / Azure fix

# Azure Portal → App registrations → Your app
# Authentication → Redirect URIs → Add URI:
https://yourapp.com/callback

Debug — find the exact URI your app is sending

# Check the authorization URL your app constructs
# The redirect_uri parameter must match the registered URI exactly

# Example authorization URL:
https://auth.yourprovider.com/authorize
  ?client_id=YOUR_CLIENT_ID
  &redirect_uri=https%3A%2F%2Fyourapp.com%2Fcallback  # URL-encoded
  &response_type=code
  &scope=openid