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

Robot account cannot access vulnerability report #17048

Closed
szczad opened this issue Jun 21, 2022 · 4 comments
Closed

Robot account cannot access vulnerability report #17048

szczad opened this issue Jun 21, 2022 · 4 comments

Comments

@szczad
Copy link

szczad commented Jun 21, 2022

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:

A robot account cannot access a vulnerability report through API.

As a developer, I want to retrieve a scan report for further processing (report generation, auditing, etc.) using non-user account.

Currently, the account can start or stop the scan but cannot retrieve scan result.

Steps to reproduce the problem:
Please provide the steps to reproduce this problem

  • Log in as the administrator
  • Go to robot accounts page
  • Create new account
  • Provide details
  • Select start scan and stop scan. No option for fetch scan.

Versions:
Please specify the versions of following systems.

  • harbor version: 2.5.1
@zyyw
Copy link
Contributor

zyyw commented Jun 27, 2022

Hi @szczad , I think this is by design, as we can see that ResourceArtifactAddition is currently not listed as one of the 19 permissions:
Screen Shot 2022-06-27 at 15 50 29

@szczad
Copy link
Author

szczad commented Jun 27, 2022

I'm not even trying to argue.

The point is - my instance has OIDC enabled so I cannot add custom users anymore. Additionally, the robotic account cannot fetch scan results. It's not even a tie. I have been defeated by the design as my report generation tool cannot fetch the list of vulnerabilities from the CI pipeline.

@MinerYang
Copy link
Contributor

hi @szczad ,
pls refer to this solution #14145 (comment)

@szczad
Copy link
Author

szczad commented Jun 27, 2022

Hi @MinerYang,

The solution seems not so smooth, but I can confirm it works if the account has artifact-addition -> read permissions!

Thanks for the workaround, however, it would be nice to have it in the UI.

@szczad szczad closed this as completed Jun 27, 2022
@szczad szczad changed the title Robot account cannot access vlunerability report Robot account cannot access vulnerability report Mar 24, 2023
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

3 participants