Add OIDC and API key authentication (issue #57)#64
Merged
Conversation
Wire up HTTP authentication for h5m's REST API. API keys use Authorization: Bearer H5M_xxx with SHA-256 hashing. OIDC is opt-in via environment variables. First user to authenticate is auto-promoted to admin. Read endpoints are public, write endpoints require auth, value purge requires admin role. Local mode provides a synthetic admin identity so existing behavior is unchanged.
barreiro
approved these changes
May 13, 2026
Contributor
barreiro
left a comment
barreiro
left a comment
There was a problem hiding this comment.
looks good.
probably should also add some @RolesAllowed annotations on the service implementations to enforce the authorization, but can be done at a later stage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wire up HTTP authentication for h5m's REST API. API keys use Authorization: Bearer H5M_xxx with SHA-256 hashing. OIDC is opt-in via environment variables. First user to authenticate is auto-promoted to admin. Read endpoints are public, write endpoints require auth, value purge requires admin role. Local mode provides a synthetic admin identity so existing behavior is unchanged.