Skip to content
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

failures on OIDC users to create robot account in their projects #20646

Closed
sicko583 opened this issue Jun 21, 2024 · 2 comments
Closed

failures on OIDC users to create robot account in their projects #20646

sicko583 opened this issue Jun 21, 2024 · 2 comments

Comments

@sicko583
Copy link

sicko583 commented Jun 21, 2024

Hi team,

We are running Harbor on v2.10.2 and with OIDC integration with Keycloak.

We happen to find that the OIDC users can not create robot account in their projects. No errors found during the creation, seems to be some frontend display issue:

image

The workaround is to grant the customer with project admin access instead of OIDC groups, then he can create robot account as expected. But this may bring another issue when login with robot account:

[root@DI2CNCTU0176WNB ~]# docker login https://harbor.xxx
Username: robot$client-test+testing
Password:
Error response from daemon: Get https://harbor.xxx/v2/: unauthorized: authentication required

some logs in core found:

2024-06-21T09:29:20Z [ERROR] [/server/middleware/security/robot.go:58][requestID="69edae9dd49c89eb0dd38c90ddeba9b1"]: failed to authenticate robot account: robot$client-test+testing
2024-06-21T09:29:20Z [ERROR] [/server/middleware/security/basic_auth.go:72][client IP="10.27.63.71" requestID="69edae9dd49c89eb0dd38c90ddeba9b1" user agent="docker/1.13.1 go/go1.10.3 kernel/5.10.16.3-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/1.13.1 \(linux\))"]: failed to authenticate user:robot$client-test+testing, error:not supported

The only way to fix that is to create a robot account in global settings, then grant project access, and it goes fine as expected.

Does this impact by robot access changes in new version?

@MinerYang
Copy link
Contributor

Hi @sicko583 ,

This is a known issue (#19928) that has been fixed in v2.11. Sorry for the inconvenience.

@sicko583
Copy link
Author

sicko583 commented Jun 21, 2024

Hi @sicko583 ,

This is a known issue (#19928) that has been fixed in v2.11. Sorry for the inconvenience.

Thanks for your help @MinerYang , I just found that v2.11.0 was released two weeks ago, I will have a try with v2.11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants