harbor icon indicating copy to clipboard operation
harbor copied to clipboard

Published 20 hours ago • verified publisher icon goharbor

LDAP - unable to add the group

Open senthil13 opened this issue 2 years ago • 4 comments

Harbor version - v2.5.1 Type of install - Helm on k8s cluster

After integrating the LDAP for authentication, everything works fine for the user but is unable to add LDAP group to the Harbor. Requesting any help will be much appreciated. I am getting two types of errors.

1.

2022-09-07T15:14:08Z [DEBUG] [/pkg/ldap/ldap.go:351]: Groupname: , groupDN: cn=XX,ou=security groups,ou=XX,ou=us,dc=XX,dc=XX,dc=com
2022-09-07T15:14:08Z [DEBUG] [/lib/http/error.go:59]: {"errors":[{"code":"BAD_REQUEST","message":"LDAP Group DN is not found: DN:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"}]}

2

Sep  7 11:52:14 172.23.0.1 core[1342]: 2022-09-07T15:52:14Z [WARNING] [/core/api/usergroup.go:56]: failed to parse user group id, error: strconv.ParseInt: parsing "": invalid syntax
Sep  7 11:52:42 172.23.0.1 core[1342]: 2022-09-07T15:52:42Z [WARNING] [/core/api/usergroup.go:56]: failed to parse user group id, error: strconv.ParseInt: parsing "": invalid syntax
Sep  7 11:52:52 172.23.0.1 core[1342]: 2022-09-07T15:52:52Z [WARNING] [/core/api/usergroup.go:56]: failed to parse user group id, error: strconv.ParseInt: parsing "": invalid syntax
Sep  7 11:52:53 172.23.0.1 core[1342]: 2022-09-07T15:52:53Z [WARNING] [/core/api/usergroup.go:56]: failed to parse user group id, error: strconv.ParseInt: parsing "": invalid syntax
Sep  7 11:53:14 172.23.0.1 core[1342]: 2022-09-07T15:53:14Z [WARNING] [/core/api/usergroup.go:56]: failed to parse user group id, error: strconv.ParseInt: parsing "": invalid syntax

Thanks Senthil

senthil13 avatar Sep 07 '22 21:09 senthil13

I'm having the same issue with v2.5.1.

koalabearskii avatar Sep 08 '22 20:09 koalabearskii

Could you paste the LDAP configuration details in harbor?

chlins avatar Sep 19 '22 08:09 chlins

2022-09-19 17_59_37-

Please find attached.

senthil13 avatar Sep 19 '22 22:09 senthil13

@chlins - do you have any update?

senthil13 avatar Nov 07 '22 14:11 senthil13

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

github-actions[bot] avatar Jan 07 '23 09:01 github-actions[bot]

@chlins - do you have any update?

senthil13 avatar Jan 09 '23 16:01 senthil13

@senthil13 from what i can tell your LDAP Group Base DN is wrong you should make it the same as the LDAP Base DN and it will probably work

acr-varonis avatar Feb 21 '23 11:02 acr-varonis

@stonezdj Please take a look, thanks!

chlins avatar Feb 21 '23 11:02 chlins

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

github-actions[bot] avatar Apr 23 '23 09:04 github-actions[bot]

Excuse me, how to solve this problem

coolsunhere avatar May 17 '23 03:05 coolsunhere

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

github-actions[bot] avatar Jul 17 '23 09:07 github-actions[bot]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

github-actions[bot] avatar Sep 17 '23 09:09 github-actions[bot]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

github-actions[bot] avatar Oct 17 '23 09:10 github-actions[bot]