-
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
Allow API access with an API-Key when OIDC is used #13093
Comments
Just encoutered that problem while trying to setup replication with Harbor as Provider. |
We're planning to enhance the robot account in the next 2.2 version. Supporting API permission is one of the items. Please stay tuned. |
@steven-zou is this delivered in 2.2.1 already? |
@Morriz take a look at #14145 (comment) and let us know if that did work for you |
got that to work! check out https://github.com/redkubes/otomi-tasks/blob/master/src/tasks/harbor/harbor.ts |
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. |
@Vad1mo does the robot v2 meet your requirement? |
In the new version(v2.8.x, v2.7.x, v2.6.x) of Harbor, you can use robot v2 to call the API of OIDC auth. |
Is your feature request related to a problem? Please describe.
When OIDC is enabled, only the admin user/credential can use the API.
Describe the solution you'd like
Harbor should extend the "Robot Accounts" with READ/WRITE API
The text was updated successfully, but these errors were encountered: