Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

What format of redirect_uri is possible to use

See original GitHub issue

I have tried to use the sample electron app. In this sample is used for the redirect_uri following link: http://127.0.0.1:8000 - and after some workflow is showed the message: Close your browser to continue. I think - it isn’t very good UX. 😃

Is it possible to use another type of processing of response then this approach with localhost - some approch with automatic closing of browser?

I have seen some redirect_uri which looks like this: com.mycompany.nativeapp://cb - where broswer is probable open inside of native app - is it possible to achieve this behaviour in this library?

Thanks for clarification!

Issue Analytics

State:
Created 5 years ago
Comments:7

Top GitHub Comments

2reactions

tikurahulcommented, Oct 11, 2018

You should use a new instance of a browser tab (because that is where the user probably has already signed in). This is the whole point of AppAuth - is to take app out of the flow and just provide a callback when the authorization step is done. That way the user is free to do things like use U2F keys etc without you having to explicitly provide support for it.

AppAuth does not support the flow you are asking for - for this reason. This is also a lot more convenient for the user as they will not be asked to enter a password if they already signed in. So UX wise I would argue that this is much better. 😀

0reactions

BTARPARcommented, Oct 25, 2019

You can do much better than that. You can have the server return a static HTML page or even run some JavaScript to close the tab automatically.

Also, you should take a look at the Electron sample app. It intercepts the localhost redirect and brings the app back into focus.

I am trying to do the same thing. I’ve hosted my static page on the server and in redirect_uri I am passing static URI but it not returning the response but if I replace it back to 127.0.0.1:8000 its working fine? Can you provide an example how you are able to redirect to static page and also able to get a response please

Top Results From Across the Web

Redirect URI (reply URL) restrictions - Microsoft Entra

A description of the restrictions and limitations on redirect URI (reply URL) format enforced by the Microsoft identity platform.

Redirect URLs - OAuth 2.0 Simplified

In these sections we will cover how to handle redirect URLs for mobile applications, how to validate redirect URLs, and how to handle...

Configuring Redirect URI Policies | Curity Identity Server

How-to work with Redirect URI Policies so that clients can use dynamic redirect URIs in OAuth flows.

Redirect URIs and Their Use Cases – Single Sign-On - WorkOS

In WorkOS Production Environments, the Redirect URI to your application must use HTTPS, however, Redirect URIs that use HTTP and localhost are allowed...

Redirect_uri - what should this contain? - Platform API

The user will be redirected to the redirect URI provided. If you use a fake URL, the user will be redirected to that...