Funder /ui/console/settings?id=login
F
FThis acts as default when no redirect target is given
FHappy to assist
FHei @shivanad.shenoy No that is not possible, as ZITADEL would not know, which url to take afterwards.
FYou mean the default redirect?
FI see, would it also work that you can send a post_register url along from your client?
FHm i think we handle it in a way that we redirect to the redirect_uri... but you can set a state that helps you understand this.
An alternative might be to use the default redirect we have, so you can define where to redirect if we do not have any
An alternative might be to use the default redirect we have, so you can define where to redirect if we do not have any
AHi @FFO so
we handle it in a way that we redirect to the redirect_urimeans that only the setting under the default redirected URI of a Organization is possible to redirect after registration? I have the same problem where I want to set a redirect for each Project
FNot sure I am totally following. Can you elaborate a little more?
Typically its best to use the state to figure out where to route in your own app.
Typically its best to use the state to figure out where to route in your own app.
Ayeah that is what I am about to test... after the first login in Zitadel I noticed there are 2 callback requests one is authorize I wonder if I can get those events on my FE OIDC, would you have some link on the doc as reference? thanks
IDear @FFO , I have a similar problem.
Desired flow: User enters his account information in our frontend, our backend creates a user via UserServiceV2().AddHumanUser(), zitadel sends an email for verification, the user clicks on the link and ends up back at zitadel, the email is now confirmed, the user logs in and is then redirected back to our frontend.
Unfortunately, this does not work.
After the email verification, the calling context is missing.
http://localhost:9300/ui/login/mail/verification?authRequestID=&code=H01X3E&orgID=298744156098920450&userID=325911803773059079
Can I pass this param via API?
This is currently blocking us from taking zitadel live
Desired flow: User enters his account information in our frontend, our backend creates a user via UserServiceV2().AddHumanUser(), zitadel sends an email for verification, the user clicks on the link and ends up back at zitadel, the email is now confirmed, the user logs in and is then redirected back to our frontend.
Unfortunately, this does not work.
After the email verification, the calling context is missing.
- If you set a ‘Default Redirect URI’, e.g. our frontend, you will be redirected there after verification, even though the user is not yet logged in; this would then be an extra step, which is super confusing and cumbersome
- if you do not set a ‘Default Redirect URI’, you will end up on the zitadel user profile page after verification and login; this is also confusing and cumbersome
http://localhost:9300/ui/login/mail/verification?authRequestID=&code=H01X3E&orgID=298744156098920450&userID=325911803773059079
Can I pass this param via API?
This is currently blocking us from taking zitadel live
AOk I ended up using my app's Login page which goes on my email link to user register... then after the whole process, he goes back because my OICD is set that way, thanks
RHi there @irieimperator! Thanks for reaching out and sharing that you're experiencing a similar issue. We'd love to help you get Zitadel running live - Let me tag in one of our engineers @Matías who can provide more insight on your case and what next steps might be. 
MHi @passionatebubbles , I'm happy to help with this question.
Instead of setting the Default Redirect URI to your application homepage, you should create an endpoint in your application, e.g.
For the users this will be seamless, after their email is verified and they click on login, they will see the login page, and will be redirected to your app after successfully logging in.
I hope that helps! Please let me know if you have any questions.
If you set a ‘Default Redirect URI’, e.g. our frontend, you will be redirected there after verification, even though the user is not yet logged in; this would then be an extra step, which is super confusing and cumbersome
Instead of setting the Default Redirect URI to your application homepage, you should create an endpoint in your application, e.g.
/redirect-login, that when called, will trigger a request to the authorization endpoint /oauth/v2/authorize with the corresponding parameters, including your app's redirect_uri, so that after authentication the user ends up in your application.For the users this will be seamless, after their email is verified and they click on login, they will see the login page, and will be redirected to your app after successfully logging in.
I hope that helps! Please let me know if you have any questions.