feat: add proxy header authentication mechanism #7151
+1,521
−75
Conversation
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
Implements a new authentication mechanism that delegates authentication to a trusted proxy. The proxy passes user identity information via HTTP headers (username, email, groups). Key features: - Configurable header names for username, email, and groups/roles - Optional trust mode that bypasses local authorization when proxy is trusted - Integration with existing authentication pipeline alongside OIDC and Basic auth - Comprehensive test coverage including both standard and trust modes Configuration properties: - apicurio.authn.proxy-header.enabled: Enable/disable the mechanism - apicurio.authn.proxy-header.username: Header name for username (default: X-Forwarded-User) - apicurio.authn.proxy-header.email: Header name for email (default: X-Forwarded-Email) - apicurio.authn.proxy-header.groups: Header name for groups (default: X-Forwarded-Groups) - apicurio.authn.proxy-header.trust-proxy-authorization: Trust proxy for authorization
The change to quarkus.http.auth.proactive=true caused authentication to execute on the Vert.x event loop thread. This broke existing OIDC basic credentials authentication which makes blocking HTTP calls to the token endpoint, resulting in 'Must not be called on event loop' exceptions. Reverting to proactive=false ensures authentication happens on worker threads where blocking operations are allowed.
This was referenced Jan 17, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Implementation Details
Configuration
New configuration properties added:
apicurio.authn.proxy-header.enabled: Enable/disable proxy header authentication (default: false)apicurio.authn.proxy-header.username: HTTP header name for username (default: X-Forwarded-User)apicurio.authn.proxy-header.email: HTTP header name for email (default: X-Forwarded-Email)apicurio.authn.proxy-header.groups: HTTP header name for groups/roles (default: X-Forwarded-Groups)apicurio.authn.proxy-header.trust-proxy-authorization: Trust proxy for authorization (default: false)Test Coverage
Documentation
quarkus.http.auth.proactiveto true for proper authentication flow