spinnaker: 1.14.X releases break Oauth integration with Google Oauth/Okta due to redirect issue.
Issue Summary:
After upgrading to 1.14.X, multiple people are reporting that their redirectUri is not being filled in correctly causing issues on redirect during oauth login.
Information about people impacted by the issue can be found in the slack thread https://spinnakerteam.slack.com/archives/C091CCWRJ/p1559273903055200?thread_ts=1558639811.086800&cid=C091CCWRJ
May or may not be related to the following pull requests/commits https://github.com/spinnaker/gate/pull/801 https://github.com/spinnaker/gate/commit/271bfab61d1f44d8ff7d4f546ec2a8efbb9b1a47
The only way to fix it at this point is the hardcode the redirectUri which causes other issues.
Environment:
Spinnaker using Oauth.
Feature Area (if this issue is UI/UX related, please tag @spinnaker/ui-ux-team):
Saml/Authentication
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 9
- Comments: 22
To give more context about this issue, I do see this error message in gate that I did not see before.
I do authn/authz with Okta and x509.
I am still seeing the issue with the v1.14.5.
Pretty sure the fix for https://github.com/spinnaker/gate/pull/844 did make it to the release-1.15.x branch. See https://github.com/spinnaker/gate/tree/release-1.15.x, https://github.com/spinnaker/gate/commit/193c7b9484d98fb55cf79581b9c1e3959ccb43fe.
Not sure what that cherry-pick failed message is about.
Still there in 1.14.7.