-
Notifications
You must be signed in to change notification settings - Fork 81
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
Using Gitlab's full_path instead of name while using authentication by Groups #181
Comments
Thanks for trying Guard, @gopigrip7. Sounds good to me, do you want to send a pr? |
cc: @nightfury1204 |
Also, group name isn't necessarily unique |
tamalsaha
added a commit
that referenced
this issue
Dec 3, 2018
Fixes #181 Signed-off-by: Tamal Saha <tamal@appscode.com>
tamalsaha
added a commit
that referenced
this issue
Dec 3, 2018
Fixes #181 Signed-off-by: Tamal Saha <tamal@appscode.com>
tamalsaha
added a commit
that referenced
this issue
Dec 3, 2018
Fixes #181 Signed-off-by: Tamal Saha <tamal@appscode.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Thanks for the guard. I had integrated with our on-premises gitlab and working great. One requirement that would help us is authentication using group/subgroup. While checking code, guard uses group name instead if its use full_path; then we can grant access subgroup level.
Thanks
Gopinath
The text was updated successfully, but these errors were encountered: