redirect_uri_mismatch when using /auth/v1/oauth2/authurl

Description

Request from a user at Exaptive, whom we are working with to support Gates Foundation-related work. They are trying to get information about things users have done in Synapse under the assumption that they have logged in via Google OAuth.

"If we can't directly fetch projects/teams and their users I hoped we could alternatively use OAuth to allow users logged into our system to "import" their projects/teams from Synapse. It looks like I should be able to use the routes:

https://repo-prod.prod.sagebase.org/auth/v1/oauth2/authurl
and
https://repo-prod.prod.sagebase.org/auth/v1/oauth2/session
to get a scoped session token that would allow me to (I hope) at least get some public information about the user.

I was going to try this out on myself, as I originally create my Synapse account via google and was able to successfully generate an authentication url to the GOOGLE_OAUTH_2_0 authentication provider but I'm not able to actually reach google, I get a redirect_uri_mismatch error. Do I need to register an application URL with Synapse before I can provide it as a redirect uri, and if so, how do I go about doing so?"

Brief chat with suggests that his redirect URLs may need to be registered similar to ORCID.

Environment

None

Assignee

Xavier Schildwachter

Reporter

Kenneth Daily

Labels

Validator

Kenneth Daily

Development Area

None

Release Version History

None

Sprint

None

Priority

Major
Configure