-
-
Notifications
You must be signed in to change notification settings - Fork 253
Question about redirect_url_path #7
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
Comments
I'm afraid I don't understand what the current experience exactly is. Can you paste your config and a browser trace, or perhaps just the URL that you end up with in the browser? |
Looks like the redirect URI that was registered with the OpenID Connect server does not match the settings of your NGINX client: it seems you will access your server on "https://sso.com" and thus you need to make sure that the redirect URI is "https://sso.com/redirect_uri". Double-check port, http/https and exact server name. |
I'm running the nginx inside vagrant, using port 3001 locally forwarding to the vagrant server. i.e. Does the port matter and would it prevent Nginx register the redirect uri? |
The port should not matter but just in case. Can you paste a browser trace? It would be interesting to see the initial URL that is being accessed and the actual redirect with the authentication request (and the redirect URL in there). |
any update on this one or was the problem solved? |
Hi,
I have a bit difficulty to get a test configuration working with Openid Connect. Everything works fine until the auth provider redirecting pages back to the Nginx
/redirect_uri
. The browser in/redirect_uri
page with all the scope, state, code parameters returnsERR_INVALID_RESPONSE
.I must have been missing something in the configuration. Do I need to add any special Nginx/Lua configuration the
/redirect_uri
URL or do I need to configure a Nginx location?Thanks in advance!
The text was updated successfully, but these errors were encountered: