Closed TS-development closed 10 months ago
After rereading the Wiki a dozen times or so I answered my own question.
This:
redirect_url: "https://www.test.org"
Is supposed to be this:
redirect_url: "https://sso.test.org/login"
It took a minute for this to process "The redirect_url
must point back to the /login
path of nginx-sso to complete the login process.", but it works as expected now!
Hello,
I'm fairly certain I'm missing something simple, what that something is escapes me. I configured the OAuth consent screen and Credentials from my GCP console. I'm testing with Nginx on host, nginx-sso in docker on the "sso" subdomain, a one pager on "www", a grafana docker on the "gf" subdomain, and "test.org" as the domain in local DNS (resolution to each subdomain works as expected).
My Nginx conf in sites-enabled looks like this:
This is all well and good, if we comment out
auth_request /sso-auth;
fromlocation /
we can resolve each subdomain normally. When we try to do SSO withauth_request
we get the redirect for the SSO login, follow the Google login prompt, and are then kicked back to the SSO login with the log output below.My config yaml is as shown (keys/hashes disregarded, as this is a local test instance):
In an attempt to suss out a misconfig, I tried to disable google_auth and try simple. In this case, I click the login button, saw a flash of what looks like username/password prompt, but got kicked right back to first login screen. Now it's no secret that skull, at any given time, is populated with 30-40% igneous rock and 60-70% gray matter, but the latter told me to run it through Burp Proxy, intercept the requests, and see if I can catch the login screen. No joy, which makes me think that a red herring and a greater underlying misconfig is present.
My authorized redirect in GCP is set to
https://www.test.org
as is mydefault_redirect
above. I think this is correct? The first log entry indicates "no valid user found", though my gmail address is set in the Test users section of the OAuth consent screen config on GCP. Then in the second log entry "invalid credentials" presumably relates to that?Are there any additional details I could provide or suggested tests?