-
Notifications
You must be signed in to change notification settings - Fork 870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnsupportedOperationException: This isn't a hierarchical URI #103
Comments
We may be able to add support for this special URI, but we currently recommend either using a custom scheme reflecting your package name or an HTTPS app link. I'm on vacation right now, I'll comment further when I get back next week. |
Unfortunately Until this Authorization Server supports custom URI schemes, as a workaround you can potentially redirect to a page on your website, which can then 302 Redirect to your custom scheme. Iain has a demo of this workaround. |
I don't see how the URI Developers just have to declare the scheme in their app manifest, just as you describe in your ReadMe: <intent-filter>
<action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.DEFAULT"/>
<category android:name="android.intent.category.BROWSABLE"/>
<data android:scheme="urn"/>
</intent-filter> No WebView required. I successfully ran a small POC in my fork with the sample provided in this repo. Am I missing something? |
So is this Authorization Server passing the authorization code as a param on the
Since supporting the older WebView OAuth patterns is a non-goal for AppAuth, I don't see us supporting this redirect option in the main repo. |
Yes, the authorization code is passed as a param on Thanks for the feedback on the POC. I'd definitely use a specific path along with the urn scheme in production code. Not supporting old patterns sounds reasonable. I appreciate the explanation and will look for alternatives. |
Hi,
I'm trying to get this library to work with the Microsoft v2 Authentication Endpoint. I'm running into the following error:
The exception is thrown in RedirectUriReceiverActivity.
The problem is that the Microsoft URI format is like this urn:ietf:wg:oauth:2.0:oob and Uri.getQueryParameter doesn't like it.
Is there any workaround to make it work with this provider?
Thanks for the great work, by the way.
The text was updated successfully, but these errors were encountered: