Configuring Auth, Callback and Token Uri at run time
See original GitHub issueIt seems that we cannot programmatically change those uris at runtime, since, the intent filter for RedirectUriReceiverActivity
or manifestPlaceholders = [ 'appAuthRedirectScheme': '' ]
has fixed values.
So theoretically with this library we cannot have a app with a settings/preference panel where we can change, let’s say the redirect uri and have the app running(building it once). For all possible redirect uri’s we have to prefil the <data android:scheme=''>
?
Is that so ?
If so then why this design decision was taken ? (I can think of custom tab implemented within an activity and scenarios similar to overriding onRedirectUrl of Webview being used to similar end)
Further with this intent forwarding model, if the user is already logged in the browser, calling Authorization request with same credential (redirected to Callback url) doesn’t get intercepted by RedirectUriReceiverActivity
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Is the redirect occuring after a user click? If the redirect is automatic (i.e. triggered by Javascript), then Chrome will not send an intent to a registered app - an explicit user action is required. There are two ways we know of to deal with this:
If the IDP supports the OpenID “prompt” parameter, pass this with value “consent” to force display of a consent screen.
Create a web page for your redirect URI that displays “Welcome back, $USER - Click here to return to the app”. Upon click, do the real redirect to the app’s custom scheme. My other demo does this to deal with GitHub, which does automatic redirect.
AppAuth redirection from chrome browser to application not working. However if we add firefox to browser whitelist by removing chrome it works perfectly fine. With firefox browser the redirection perfectly works fine. Chrome app version is 79.0.3945.136