I am developing a Chrome extension that uses chrome.identity.getAuthtoken
API – to handle Google OAuth 2.0 authentication.
-
In Chrome browser it’s working fine.
-
However, this API is not supported in the Microsoft Edge browser (link here). So as per suggestions in multiple forums, I am trying to use
chrome.identity.launchWebAuthFlow
API to handle Google OAuth 2.0 authentication for Microsoft Edge.But the
chrome.identity.launchWebAuthFlow
API is not working & is returningError 400: redirect_uri_mismatch
I couldn’t find any documentation or discussion explaining this behavior on Edge or other Chromium-based browsers.
m questions-
Q1. Is there a specific configuration required in the Google Cloud Console to support other Chromium-based browsers (like Edge) when using Chrome.identity.launchWebAuthFlow
?
Q2. Does Edge handle chrome.identity.launchWebAuthFlow differently, causing it to reject the redirect_uri?
Are there any known limitations or workarounds for this issue in Chromium-based browsers other than Chrome?