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

Custom authentication mechanism is not invoked when no identity providers are registered #38508

Closed
sberyozkin opened this issue Jan 31, 2024 · 1 comment · Fixed by #38842
Closed
Assignees
Labels
area/security kind/bug Something isn't working
Milestone

Comments

@sberyozkin
Copy link
Member

sberyozkin commented Jan 31, 2024

Describe the bug

Security architecture assumes that the current HTTP Authentication mechanism only extracts the credentials and passes them to the registered identity providers.

It makes total sense but should not be enforced, when a simple mechanism already has the knowledge how to create an identity

Expected behavior

IdentityProviderManager should log when it is invoked and zero providers are available and report an authentication failed exception to protected against such cases but HttpAuthenticator should give a chance to the registered HTTP mechanisms

Actual behavior

HttpAuthenticationMechanism is ignored when no IdentyProvider is registered

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

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