Login V1 to Login V2
We are migrating from Login V1 to Login V2.
We already are in production with Login V1.
After hosting the login V2, and configuring our zitadel instance organization to redirect to the new login ui v2.
When our front app call the "authorization"
https://idpxxx.instance.com/oauth/v2/authorize?client_id=xxxx&redirect_uri=https://webapp.xxxx.com/idp-callback
The authorize redirect correctly to the new login V2.
We are able to authenticate, BUT after authentication, the new login v2 redirect to idp and does not take care about the "redirect_uri" given in the authorize parameters.
Any idea ?
The redirect url to the new login v2 :
https://login.xxx.com/ui/v2/login?authRequest=V2_xxxx
and then redirect to :
https://login.xxx.com/ui/v2/login/loginname
So the redirect_uri is not transmitted to the new login v2
Thank you
We already are in production with Login V1.
After hosting the login V2, and configuring our zitadel instance organization to redirect to the new login ui v2.
When our front app call the "authorization"
https://idpxxx.instance.com/oauth/v2/authorize?client_id=xxxx&redirect_uri=https://webapp.xxxx.com/idp-callback
The authorize redirect correctly to the new login V2.
We are able to authenticate, BUT after authentication, the new login v2 redirect to idp and does not take care about the "redirect_uri" given in the authorize parameters.
Any idea ?
The redirect url to the new login v2 :
https://login.xxx.com/ui/v2/login?authRequest=V2_xxxx
and then redirect to :
https://login.xxx.com/ui/v2/login/loginname
So the redirect_uri is not transmitted to the new login v2
Thank you
