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

Scorecard action fails when using fulcio - in prod sometimes #919

Closed
naveensrinivasan opened this issue Dec 13, 2022 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@naveensrinivasan
Copy link
Contributor

Description

When signing scorecard results, the prod fulcio fails.

Retrieving signed certificate...

        Note that there may be personally identifiable information associated with this signed artifact.
        This may include the email address associated with the account with which you authenticate.
        This information will be used for signing this artifact and will be stored in public transparency logs and cannot be removed later.
Non-interactive mode detected, using device flow.
Enter the verification code SNGK-RDRS in your browser at: https://oauth2.sigstore.dev/auth/device?user_code=SNGK-RDRS
Code will be valid for 300 seconds
2022/12/10 06:18:37 error signing scorecard json results: error signing payload: getting key from Fulcio: retrieving cert: error obtaining token: expired_token

https://github.com/ossf-tests/scorecard-action/actions/runs/3662971555/jobs/6192441160

@cpanato
Copy link
Member

cpanato commented Dec 13, 2022

looks like in this case that is missing the GITHUB_TOKEN that should contain the OIDC permission, looks like that job is using SCORECARD_READ_TOKEN

@bobcallaway
Copy link
Member

Right - CI runs on Github Actions shouldn't be using the device code flow, but rather using ambient OIDC tokens

@naveensrinivasan
Copy link
Contributor Author

Sounds good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants