This document provides troubleshooting guidance for OAuth2 integrations, including some common issues. For further assistance, contact Edlink support or your Customer Success Manager.
Common Issues & Resolutions
Addressing common OAuth2 issues early can help ensure a smooth integration and prevent disruptions for users accessing connected platforms.
Mismatched Emails/Usernames
- Issue: Person not found.
- Potential Resolution: Verify that the email or username in the primary data source matches the identifier in the OAuth2 provider exactly.
Login Failures
- Issue: Authentication fails during login.
- Potential Resolution: Confirm that the OAuth2 provider setup (e.g., client ID, client secret, redirect URI) is correctly configured within Edlink.
- Potential Resolution: Check the OAuth2 provider configuration to ensure the application is set up with the appropriate redirect URI and scopes.
Unsupported Provider
- Issue: The OAuth2 provider does not fully comply with OAuth2 standards.
- Potential Resolution: Switch to a provider that adheres to OAuth2 specifications.
- Potential Resolution: Verify that the provider supports the required grant types (e.g., Authorization Code Grant, Client Credentials Grant).
Scope Issues
- Issue: Users do not have access to required data.
- Potential Resolution: Check that the requested scopes in the OAuth2 configuration (e.g.,
openid,email,profile) match the data required for the integration. - Potential Resolution: Update the scope settings in both the OAuth2 provider and the Edlink configuration.
- Potential Resolution: Check that the requested scopes in the OAuth2 configuration (e.g.,
For further assistance with OAuth2 troubleshooting, contact Edlink support or your Customer Success Manager.