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

OIDC hardening and defining trust misses some values from subject claims #34016

Closed
1 task done
janbrasna opened this issue Jul 18, 2024 · 4 comments
Closed
1 task done
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue waiting for review Issue/PR is waiting for a writer's review

Comments

@janbrasna
Copy link
Contributor

janbrasna commented Jul 18, 2024

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims

What part(s) of the article would you like to see updated?

"instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use."

And then the following chapter demonstrates filtering for branches, environments, tags, and pull_request events.

That would lead me to expecting the tags and events in the quoted paragraph as well.

Additional information

Adding the tags seems straightforward, including the pull request events will need a bit more verbosity or changing that sentence around a bit.

Or, the sentence can be reworded to be taken as an example only, not providing the complete list of options.

@janbrasna janbrasna added the content This issue or pull request belongs to the Docs Content team label Jul 18, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 18, 2024
@janbrasna
Copy link
Contributor Author

(I won't even attempt at fixing this myself as the :octocat:-bot will tell me not to touch anything there, so I'll leave that to others to decide/fixup…)

@nguyenalex836 nguyenalex836 added actions This issue or pull request should be reviewed by the docs actions team waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Jul 19, 2024
@nguyenalex836
Copy link
Contributor

@janbrasna Thanks so much for opening an issue! I'll get this triaged for review ✨

@sunbrye
Copy link
Contributor

sunbrye commented Jul 25, 2024

@janbrasna Thank you for bringing up this source of confusion regarding the documentation about "Example subject claims".
Since this article is restricted by a CODEOWNERS file, we will transfer this internally and work on this fix.

@sunbrye sunbrye added the fix-internally Triggers a workflow to copy the issue internally and close the current issue label Jul 25, 2024
@docs-bot
Copy link
Collaborator

Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

No branches or pull requests

4 participants