[GitHub] cordova-plugin-inappbrowser issue #99: inAppBrowser custom application schem...

[benbotto <gi...@git.apache.org>]

Github user benbotto commented on the issue:

    https://github.com/apache/cordova-plugin-inappbrowser/pull/99
  
    It's really been a long time waiting for this, over two years now!  My team has been manually patching this piece of code to support custom application URIs for over a year.  I'm not familiar enough with the Cordova code or project management to know why the iOS code changes are in there, or if there is a related JIRA ticket.  That said, it sure is inconvenient that custom URIs work differently between iOS and Android.  It seems like either both should work with custom URI schemes, or neither should (my vote's of course for the former).
    
    Anyway, if adding application URIs in an InAppBrowser is not a good idea, then maybe someone can chime in on how to correctly implement something that requires a redirect back to an app.  For example, we use OpenID Connect as a single sign-on solution.  As part of the OpenID Connect spec the user agent (the mobile app) sends the user to a web page to authenticate.  Then, on successful authentication, the user is redirected back to the client with an access token and id token.  That redirect back requires handling a custom URI scheme, and it does not work in Android.
    
    There's a long list of folks affected by this, and it's a burden for your users to have to use custom forks to implement something as common and simple as OAuth2.  That's especially true since the solution, at least ostensibly, seems trivial.  I for one would really appreciate a fix!


---

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org