Troubleshooting
Callback (redirect URI) mismatch
What a redirect URI mismatch means after a provider redirect, and how workspace owners resolve it.
A callback mismatch appears when the address a provider redirects back to does not exactly match the redirect URI registered with that provider. Providers reject the request for safety, and OSTaaS shows a friendly failure with a reference ID rather than a raw provider error.
Why it happens
- The provider app registration lists a different redirect URI than the environment is actually serving.
- The site is being reached on a different origin (for example a preview URL vs. the production domain) than the one registered.
How owners fix it
- Confirm the exact callback URL for the provider — it is provider-specific and ends in the provider's callback path.
- In the provider's app registration, ensure that exact URL is listed as an allowed redirect URI (scheme, host, and path must all match).
- Save, then retry sign-in.
Regular members cannot fix this — it is a configuration change. Share your reference ID with your workspace owner or operator.
Related
Related documentation
- Microsoft sign-in troubleshootingResolve Microsoft Entra ID (Azure AD) sign-in errors such as consent, tenant restrictions, and redirect mismatches.
- OAuth authorizationHow OSTaaS uses OAuth 2.0 to connect repositories and third-party services on your behalf.
- Sign-in troubleshootingResolve the most common Microsoft and social sign-in problems, using the reference ID from the sign-in result screen.