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

GitHub actions OIDC #64

Merged
merged 11 commits into from
Aug 12, 2024
Merged

GitHub actions OIDC #64

merged 11 commits into from
Aug 12, 2024

Conversation

holesch
Copy link
Owner

@holesch holesch commented Aug 12, 2024

The --token-cmd argument can be used as an alternative to not-my-board login in non-interactive environments, like CI.

holesch added 11 commits August 10, 2024 15:33
Try reading config file location from environment variable, before
falling back to the default path.
This can be used to generate an ID token from an external source, for
example GitHub Actions OIDC tokens.
The get_id_token() method was never registered with the websocket
channel, so the hub couldn't get an ID token from the agent.
Don't try to load the vhci-hcd Kernel module, when calling `not-my-board
status`. The Kernel module is only necessary when the user tries to
attach a USB device.
Some issuers don't have all the provider metadata, that is required by
the OpenID Connect Discovery specification. For example GitHub Actions
doesn't have the `authorization_endpoint`. To validate a token, this
endpoint is not necessary, so only require it for login, but not for
validation.
Use token source classes to hide the details from users. There are two
sources: from file and from command.
@holesch holesch merged commit 70a2490 into master Aug 12, 2024
9 checks passed
@holesch holesch deleted the github-actions-oidc branch August 16, 2024 17:00
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

Successfully merging this pull request may close these issues.

1 participant