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
Redirect uri #23
Comments
@eugedebe can you try providing the uri as a route within the flutter app ? |
For me, the solution was going from a redirect url like this:
to a standard weburl like this:
Both of these was configured in my tenant, so it was an easy fix. Otherwise you need to find you app-registration in Azure Portal and add a new allowed redirect-url. |
closing as solution provided by @filip8600 . Thanks! |
Hi,
First of all thanks for this library
I have implemented the code given in the example in pubdev. After pressing the button, I am able to receive in the callbacks of the widget (onIDToken and onAnyTokenRetrieved) receiving correctly the token given by B2c auth. The callback onRedirect is also being call correctly and i am able to navigate to another screen (my home screen). My only issue, is that after logging in the browser can't find the redirect url of the schema, the message shown in the browser of the mobile phone after login is: .com.example/authapp://oauthredirect/?code........ could not be loaded because net::ERR_UNKNOWN_URL_SCHEME
I had created (in android) a schema in the manifest adding in the activity tag
I tried to handle the url by installing the library uni_links and adding a listener in the main function :
But when I debug the code, the breakpoint in the listener (breakpoint in line if (link != null &&
link.startsWith('com.example.authapp://oauthredirect')) ) is never reached.
I am a little bit lost what I need to do in order to show instead of a broken url text a loading progress or something like that during this fraction of second between the the token retrieved and the redirect callback that is sending the user to the home page.
Thanks.
The text was updated successfully, but these errors were encountered: