Repository navigation
Mobile App Flow #22530
|
Hi, I am currently building mobile apps and was wondering what the best user flow is from keycloak's pov. I can obviously easily login using an OAuth2 client with a native UI. That's the easy part. |
Replies: 4 comments 3 replies
|
The best practice for OAuth2 for the mobile flow for a native mobile application is detailed in RFC 8252 - OAuth 2.0 for Native Apps in which you are using the OpenID AppAuth (AppAuth Android / AppAuth iOS) libraries which will be using an in-app browser tab to navigate to the authorization endpoint. In which case they would be using the in-app browser for filling in the registration form. |
|
Hi, we are using AppAuth to SignIn/SignUp with Keycloak using Email, Google, Facebook and Apple and so far all good. But the experience in iOS is not ideal because every time the user is going to login, a mandatory iOS AlertDialog shows up indicating the app is going to access our Keycloak domain and this is not a good user experience from my point of view. |
|
If you think the dialog impacts usability you can use the |
|
Hi thanks for your feedback, yeah exactly
The point of all of this is that the user stays within the app when they decide to SignIn/Up manually because would be the app’s own IDP, then if the user decides to SignIn/Up using Social Login then it’s expected to go outside the app interface as this is an external IDP but a known IDP I mean the user already knows and trust google.com, facebook.com but not auth.myapp.com. |
|
I guess the simplest approach to still comply with the patterns, would be to inform the user about the warning before the warning appears. Something like: "... you will access our servers at APP_DOMAIN.COM/path. Please check if that is the address appearing in the address bar in the next screen". |
|
So , Any one find a way to use native app login form to use keycloak without use browser or in-app browser/tab. There is way we can use post api but it's use client secret key. So anyone have way to use native login flow for android share it here please. |
|
There basically isn't a way to do this. |
The best practice for OAuth2 for the mobile flow for a native mobile application is detailed in RFC 8252 - OAuth 2.0 for Native Apps in which you are using the OpenID AppAuth (AppAuth Android / AppAuth iOS) libraries which will be using an in-app browser tab to navigate to the authorization endpoint. In which case they would be using the in-app browser for filling in the registration form.