goharbor / harbor

An open source trusted cloud native registry project that stores, signs, and scans content.
https://goharbor.io
Apache License 2.0
23.15k stars 4.67k forks source link

Support nested LDAP groups #8122

Open mungo312 opened 5 years ago

mungo312 commented 5 years ago

In our company we are using nested groups in our Active Directory. This means: User <-> OrgGroup <-> ResourceGroup The resource group is configured in Harbor

At the moment the Group membership is not detected in harbor, in my tests the user did not get admin privileges.

Steps to reproduce the problem: Use a LDAP with nested Groups.

Versions: Please specify the versions of following systems.

Typositoire commented 5 years ago

Any idea when this will be actually done ?

Typositoire commented 5 years ago

Actually I've got a really crud implementation if you guys are interested ?

ConorNevin commented 4 years ago

I believe this change was rolled back - maybe this should be reopened and moved back into the Backlog?

narendrakum commented 3 years ago

Few of the customers using harbor tile in TKGI environment requested for nested ldap group support. Spoke with engineering and reopened this issue.. Current harbor version: 2.1.1

gwiersma commented 2 years ago

Following this issue. Our organization really needs this feature.

vikingtoby commented 2 years ago

Agreed, this is essential for us as well.

hashCode1 commented 2 years ago

same this is important for us

lavih commented 2 years ago

I will be more than happy for this feature as well :)

jpistoor commented 2 years ago

Hi, we also would like to be able to use nested groups in Harbor so will follow this issue as well.

RobMokkink commented 2 years ago

This RFE is open for a long time now, any thoughts when this will be implemented?

xcorp commented 1 year ago

Chiming in to request this to. This issue is also very similar to https://github.com/goharbor/harbor/issues/9492

robertdebock commented 1 year ago

I see the issue is in the "v1.9 completed" row of the Harbor Project Board.

On the other hand, I see this issue is assigned to the backlog if candidate/2.7.0

This issue is open however.

The related issue is in the "prioritised backlog"

Is there anything we can do to improve the issue so it can be picked up?

kkrombach commented 6 months ago

Hello, we also would love to see this feature in our company :)

larsl-net commented 1 month ago

Hi, are there any plans when this will be integrated? Without this, we need to maintain the permissions/group assignments multiple times.