OAuth2 consent page does not seem to be optimized for mobile devices

Question

Hello Lucid developers!At my work I'm trying to add Lucid export to one mobile app. According to the documentation I'm trying to redirect a client from my mobile app to a web browser at https://lucid.app/oauth2/authorize (plus necessary parameters).And in a mobile browser (more precisely android’s Custom Tabs), after logging into Lucid, the user sees such a screen (see screenshot). It doesn't seem to be optimized for mobile devices. It seems even not horizontally scrollable. Can you (Lucid developers) fix this? Or maybe I can fix this from my side somehow?I also have two less important questions.1) The user of the mobile application can log in through a web browser, after which the application receives an authorization code and the necessary tokens. After this, the user may want to unlink the mobile application from his Lucid account and we call the API here (https://developer.lucid.co/rest-api/v1/#oauth2-revoke-access-token). After which the user may want to log in to Lucid again with a different Lucid account, but when the mobile application redirects him again to https://lucid.app/oauth2/authorize, the user is no longer able to see the login screen, and he is immediately redirected back to the mobile application (because its session is not closed in the browser - it is already logged in in the browser). I know that some OAuth providers have a special parameter for the authorization endpoint like prompt=login . Maybe you have something similar?2) Not a very important question - will OAuth redirect work if the user is not yet registered in Lucid? That is, will a redirect from https://lucid.app/oauth2/authorize back to the mobile application work if the user starts the process of registering a new Lucid account?

Ian Baenziger · Accepted Answer

Okay! Hey Fedir! Sorry this took a day later than expected.

1) I know that some OAuth providers have a special parameter for the authorization endpoint like prompt=login . Maybe you have something similar?

We unfortunately do not currently offer the “prompt=login” flow/parameter. Do you expect users to often be switching amongst multiple Lucid accounts when using your app? Trying to gauge the importance of this functionality for your build.

2) Will OAuth redirect work if the user is not yet registered in Lucid?

The technical answer here is “sorta” 🙂. Short version: the user will be asked to create an account, but won’t be auto-redirected.

Longer version: when the user does not have a Lucid account and they try to click the link to the grant access page on mobile, the user will be prompted to login or create an account. After they create an account they will hit a page that looks like the screenshot below (note the page shown below is not the mobile version). The user will need to then re-click the link to the grant access page to use the app.

Note this is an experience we likely won’t change in the near future (just given other things on our roadmap).

Ian Baenziger · Answer

Hey Fedir!In complete transparency, mobile development on our REST API is relatively new territory for us, so thank you for your question and post! This is an area we’re excited to improve.We have discussed internally and now have a developer actively working to make our OAuth 2 Grant Access page mobile responsive. We do not yet have an ETA, but I do not expect it to take very long.Regarding your other two questions, we will get back to your tomorrow. We have an API team meeting tomorrow morning that I want to discuss the topic then.Will get back to you more tomorrow. Thanks!

OAuth2 consent page does not seem to be optimized for mobile devices

Comments

1 Attachment

Reply

1 Attachment

Reply

Create an account in the community

Login with SSO

Log in to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded