-
Notifications
You must be signed in to change notification settings - Fork 702
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
Allow to bypass the oauth loading page #2149
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks.
@@ -1,6 +1,6 @@ | |||
apiVersion: v1 | |||
name: kubeapps | |||
version: 4.0.4 | |||
version: 4.0.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe land this after @antgamdia 's PR with the ClusterRole, so they're both included in the chart update (once you've reviewed his).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, @antgamdia changes cannot be used until the new endpoint (/refresh
) is available so the change in the chart is not going to be usable yet.
} else { | ||
dispatch(setAuthenticated(false, false, "")); | ||
return false; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps just
return isAuthed;
instead?
mount(<LoginForm {...defaultProps} checkCookieAuthentication={checkCookieAuthentication} />); | ||
expect(checkCookieAuthentication).not.toHaveBeenCalled(); | ||
}); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are these removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because this was already been covered in the tests under "oauth login form" (sorry I forgot to mention that).
Description of the change
As per #2109, allow users to configure Kubeapps so it skips the login/welcome page and redirect directly to the OAuth login URI.
To use it, a value is exposed in the chart:
--set authProxy.skipKubeappsLoginPage=true
.Applicable issues