Device Auth custom login v2 URI
❓Question🪲Bugs✅Solved
Hey, we are building our own Login UI and currently integrating the device authorization flow from the zitadel guides/docs.
https://zitadel.com/docs/guides/integrate/login-ui/device-auth#device-authorization-request
We have run into an issue regarding setting the custom URI to our own Login UI.
It's setup in the features section for the whole Zitadel instance and working fine on the other OIDC flows. For the device code application we have enabled "Use new Login UI" with our own custom base URI setup. However when receiving the verification uri, it will still redirect to the old hosted login page.
Are we missing something?
https://zitadel.com/docs/guides/integrate/login-ui/device-auth#device-authorization-request
We have run into an issue regarding setting the custom URI to our own Login UI.
It's setup in the features section for the whole Zitadel instance and working fine on the other OIDC flows. For the device code application we have enabled "Use new Login UI" with our own custom base URI setup. However when receiving the verification uri, it will still redirect to the old hosted login page.
Are we missing something?
Implement the OAuth 2.0 Device Authorization Grant in your custom login UI for browserless devices.
