Configuring OAuth Redirect URIs for SSO Integration

When setting up OAuth SSO integration, you may encounter "invalid redirect URI" errors. This happens when the redirect URI sent in your OAuth request doesn't match the URIs configured in your OAuth application settings.

Understanding Redirect URIs

OAuth applications require pre-configured redirect URIs for security purposes. These URIs must exactly match what your application sends during the OAuth flow, including the protocol (http/https) and any subdomains.

Common Redirect URI Issues

The most common causes of redirect URI errors include:

• Protocol mismatch (http vs https)

• Subdomain variations (with or without "www")

• Different callback paths

• Domain changes during development or production deployment

Configuring Multiple Redirect URIs

You can configure multiple redirect URIs to handle different scenarios:

• Development and production environments

• Different subdomain variations (example.com and www.example.com)

• Both HTTP and HTTPS protocols if needed

For example, you might configure:

• https://example.com/*

• https://example.com/callback

• https://www.example.com/*

• https://www.example.com/callback

Resolving Redirect URI Errors

If you're experiencing redirect URI errors:

1. Check the exact URI being sent in your OAuth request

2. Verify it matches one of the configured redirect URIs exactly

3. Pay attention to protocol (http vs https) and subdomain differences

4. Contact support to add additional redirect URIs if needed

Testing Changes

After updating redirect URI configurations:

1. Test the OAuth flow thoroughly on your staging environment

2. Verify both new user registration and existing user login flows work correctly

3. Confirm all required user data is being passed correctly

4. Only move to production after successful staging tests

If you need additional redirect URIs configured for your OAuth application, contact support with the specific URIs you need added.