-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Disable anonymous user #10760
Comments
@reasonerjt I am reading the Harbor codes, could you pls help check if we can remove this section to disable the anonymous access? https://github.com/goharbor/harbor/blob/v1.10.1/src/core/api/project.go#L406 Thanks |
Obviously, this is a requirement and then needs the decision from PM. |
Anonymous access is good for community purpose; and for Enterprise, the public repo should be only visible for authenticated people to protect the content and IP - so pls add the configuration item to enable/disable anonymous. Before it's available, can we quickly fork and make some changes as I proposed above? Do you think it's the only place I need to change? Thank you again for such great open source software. ye |
I got a similar request from "Xing ye Yin hang". |
I submitted a PR #10825. Thanks |
agreed, makes sense for a lot of customers |
I agree it's a valid requirement but we should put it in the pipeline and write proposal, then target it to a release, no? |
I will make the document, thanks for your information. |
@xaleeks I created the document with a PR in the harbor community repo at goharbor/community#124. Thanks |
@cafeliker Thanks, I think it looks good. |
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. |
Hi Any update in this feature? Would be nice to have this for handling some analytics |
Hello Team, any update on this feature implementation? |
we are using Harbor internally and using OIDC provider for the auth. we don't want anonymous access for this instance. we'd like to keep all public project only accessible by authed users. it's possible to make this configurable ? if code change needed, anyone can help to share this changes?
thx!
The text was updated successfully, but these errors were encountered: