You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 mechanismsActual behavior
HttpAuthenticationMechanism is ignored when no IdentyProvider is registered
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: