Intent has not succeeded
On implementing my own UI I struggle to login with google.
After selecting a Google account and being redirected to the
After selecting a Google account and being redirected to the
/idp/google/success page, I'm immediately redirected back to the Google account selection screen. This creates an infinite loop.
I checked the logs and found the following error:
18 Replies
hey @anhtuan159 thanks for your question, did you follow any docs while building your own UI?. Can I have a look at it?. What version aree you on as well?.
Thanks
Hey @Rajat Singh thank you for your message!
I've identified the issue. It happens during the account linking process. When I log in using the Google provider, a sessionId is created, but it's not yet reflected in the session list 😦
Do you have any suggestions on how I can fix this?
Hey @anhtuan159 I might have to look a bit more deep in it. I'll get Back to you with that information
Thanks! I’ll wait for your update
hey guys, do you have an update on this? We're having the same issue
hey @JoseSzycho I have setup google IDP a couple of times since it was asked and now it works fine, pls give it a try again https://zitadel.com/docs/guides/integrate/identity-providers/google
🙂
Make sure:
"Account creation allowed" or "Account linking allowed" is enabled for your Google IdP in ZITADEL
@Rajat i tried to enabled both, but i still got same error.
hey @yahya can u pls share some more info/screenshot
@Rajat so, i'm using custom auth ui https://github.com/zitadel/typescript for my auth app (self hosted). And I found an issue for users who have Google Login + 2FA enabled. where the user is redirected to a link with this format after select the google account
i checked the log, and i got
IntentGitHub
GitHub - zitadel/typescript: Typescript packages and application to...
Typescript packages and application to showcase the ZITADEL resource API - zitadel/typescript
hey @yahya how are you handling
{app_auth_url}/login?? when I see your message
this seems wrong
{app_auth_url}/loginhttps://accounts.google.como/oauth2/v2/auth?
it shoud be https://accounts.google.com/o/oauth2/v2/auth?...
are you prefixing this {app_auth_url}/login?.Nope, it’s the default path from the typescript repo. The full url is
‘https://{domain}/ui/v2/login/[route]
good morning @yahya I will look into it 🙂
Thanks @Rajat hopefully there will be good results
Morning @Rajat Is there any new information regarding this issue? especially for the route issue
hey @yahya I will look into it today, thanks
raised it internally 🙂
@Rajat my team also can replicate this issue with the fresh setup in local using zitadel docker-compose. our testing flow until we got the issue was
1. Register using Google
2. Enable 2FA
3. Log out
4. Login using google
and then you'll get
if i disabling the 2fa, the user can login without any issue
hey @molla good mornining, thanks for the steps to replicate this, my team was asking for this step. I will forward this internaly
I will test it on docker, BUT it works very well on cloud with no issues.
whe you say
and then you'll get {app_auth_url}/loginhttps://accounts.google.com/o/oauth2/v2/auth?client_id={client_id}&prompt=select_account&redirect_uri=https%3A%2F%2Fauth.staging.net%2Fidps%2Fcallback&response_type=code&scope=openid+profile+email+phone&state={state}where exactly are you getting this error? Is it in Network tab or in the logs?. Thanks
That is the url that i got after callback from google. And i got that error when using the latest zitadel version (v4) or with the zitadel custom auth ui (typescript)
Currently our team is using self-hosted.