Open im4everok opened 10 months ago
For most cases, no extra flows need to be configured/created for social authentication. Adding the source in the identification stage in the default-authentication-flow
, using the default-source-authentication
as authentication flow for the source and default-enrollment-flow
as the enrollment flow for the source should work without any loops
We are trying to login to our SPA application ( .net + react ) using authentik as wrapper for GCP project.
How should authentication / authorization / enrollment flows look in order for user to be able to login to application with Google social login?
Currently we have a problem that it is possible to enroll for an application, but if user is already created, and then you try to login when user exists, the authentik starts redirecting you in an endless loop of: Authentik ( authentication-flow with Google source) => auth.google.com => user logins via google on Google embedded page => return to authentik callback => cycle repeats.