Prasanth Baskar
Prasanth Baskar
Hello @TMHBOFH Thanks for the work you had done. I have reviewed the code looks good. but hardcoding nested group support behind a checkbox limits flexibility. In real enterprise LDAP...
@TMHBOFH try setting the `ldap_group_admin_filter` value to `(memberof:1.2.840.113556.1.4.1941:=cn=harboradmingroup,ou=groups,dc=example,dc=com)` this filter will capture admins with nested groups under the `harboradmingroup`. Hope this helps!! :)
@stonezdj We already have LDAP filter for filtering normal users. in this PR we are extending the same to filter admin users. Hope this helps
> I had a similar issue where i had 401 error via cli: the issue in my case was due to a misconfiguration where the core harbor user password was...
> @bupd could you put the file content in link https://pastebin.com/em9MVQXR to your personal github repo? we can't access it. @carsontham
IMO, the retention policy should be set on Harbor on which you are actively pulling the image. Since every harbor deployment is independent to the other it is not possible...
@Aloui-Ikram Once again, thanks for clearing up my backlog.
looks like the UTTEST is flaking again.
There is currently ongoing work on arm support by @ranimandepudi and already there are some ARM images built by the community PTAL https://github.com/goharbor/community/pull/262 I believe @ranimandepudi could help here.
/label good-first-issue