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

1.13.0 broke our workflow, downstream auth error #51

Open
jessfraz opened this issue Aug 7, 2024 · 2 comments
Open

1.13.0 broke our workflow, downstream auth error #51

jessfraz opened this issue Aug 7, 2024 · 2 comments

Comments

@jessfraz
Copy link

jessfraz commented Aug 7, 2024

1.12.0 does not have this issue

our workflow goes:

  1. login to ghcr.io
  2. login to docker hub where we have scout access
  3. build image
  4. push image to ghcr.io
  5. scan image

this is the error we see on 1.13.0 we are not seeing on 1.12.0

cves
      ...Storing image for indexing
      ✓ Image stored for indexing
      ...Indexing
      ✓ Indexed 412 packages
      ✓ Provenance obtained from attestation
  Error: could not list CVEs for the image: API operation failed: Message: Not allowed, Locations: [], Extensions: map[arguments:map[context:$context query:map[imageCoords:map[digest:$digest hostname:$hostname repository:$repository] includeExcepted:$includeExcepted packageUrls:$purls]] code:DOWNSTREAM_SERVICE_ERROR status:FORBIDDEN], Path: [vulnerabilitiesByPackageForImageCoords]
Screenshot 2024-08-06 at 11 57 44 PM
@eunomie
Copy link
Contributor

eunomie commented Aug 7, 2024

Thanks @jessfraz for the report.
I'm able to reproduce it, looking at it and will keep you posted once fixed.

@eunomie
Copy link
Contributor

eunomie commented Aug 7, 2024

@jessfraz It looks like the organisation you're using is not enrolled to docker scout and that causes the issue. As it's not enrolled we can't get specific data based on it.
This is due to the inclusion of vulnerability exceptions that are now tight to organizations (so they can be defined in the UI).

So either you can enroll your organisation using docker scout enroll <your-org> or not set organization in the action parameters.

In the mean time we are working at improving the error handling and messages so that the problem will be more understandable and the user experience better.

Hope this will solve your issue.

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