-
Notifications
You must be signed in to change notification settings - Fork 327
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
Add GitLab provider #515
Add GitLab provider #515
Conversation
@cbjartli this looks pretty good without testing it personally. I think this would accommodate gitlab self-hosted, is that right? |
@bnfinet, it should, by providing the |
bf72b09
to
d6bf9ff
Compare
@bnfinet I've tested it against a self-hosted instance, and it seems to work as expected. I modified the example config so that it contains the relevant configuration details for the case of self-hosted instances too. |
f8bb682
to
9f80f3d
Compare
@cbjartli thanks for testing self hosted! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@cbjartli sorry for the delay in reviewing. Thank you for the contribution to VP. I have setup a self hosted instance of GitLab and I have tested VP with GitLab. The basic login functionality works well. It does not appear that any logic has been added in order to validate that a user's group is present on the configured Something similar to the check in Also it could use some tests. |
@cbjartli also please follow conventions for |
@bnfinet Thank you for the review, will go through the issues raised asap.
This is strange, we have this in internal use, and it certainly only allows users whose group belongs to the whitelist through. I distinctly remember adding a check for this. I am not in front of my computer now, but I'll have to get back to you. (Could simply be an issue of a missing push.) |
Hi. Why pr was closed? |
@nrukavkov please see conversation in #514 |
There does not appear to be any conversation with the author after opening the PR |
@puttehi that's just not the case. Please take a closer look. This PR doesn't work, it's incomplete, it's missing code that the author used in his environment. @cbjartli asked his colleague to submit an alternate solution (see #514). I'm still hopeful that will result in a working solution. If anyone else would care to submit a working PR I'll happily test it out. GitLab group based auth would be a nice addition to VP. |
Apologies for being away due to life and work events. Will try to give this matter some attention asap. I just want to note that @ritmanda is not a colleague of mine as far as I know, so we have not communicated about a solution to this issue. |
This patch adds direct support of GitLab as identity provider. The provider gets information about the user's groups from the
groups
claim, and makes it possible to whitelist users by GitLab group membership. This patch extends theteamWhitelist
keyword, which until now was only valid for the GitHub provider, to also be valid when used with the new GitLab provider.Resolves #514.