Sounds reasonable. I recommend looking at the following first though before
you start implementation AppAuth [1] and OAuth 2.0 for Native Apps [2]
[1]
Hi there,
I would like to pick up an old issue: KEYCLOAK-2606<https://issues.
jboss.org/browse/KEYCLOAK-2606>
Our current app uses Keycloak with the Cordova In-App-Browser. Technically
this works fine, but the user experience is … uhmm … awful. The page
renders quiet slow and has focus issues.
I’d love to help getting some support for the browser-tab. I started
porting the ionic sample app to browertabs, but would like to check back
with you before doing something stupid.
The idea is:
1. In Keycloak.js Cordova Adapter check if browertab is supported, else
fall back to in-app-browser
2. Open the login-page with the In-App-Browser (leaving the app)
3. Register a custom-url-scheme and configure it as redirect url (i.e.
keycloakapp://). We’ll need another Cordova plugin for this (i.e. deep
links). The Cordova-Adapter needs to get extended for this, since
„localost“ seems to be hardcoded as redirect-url)
4. The Keycloak-server will redirect to the app after login succeeded. The
App will need to reinitialize the Keycloak-Adapter with the code given in
the url - I’m not sure if this will work out of the box.
Does this sound reasonable?
Thanks,
Gregor!
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev