-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
False
-
None
-
False
-
---
-
-
Fixes #35975.
The current verbose error reporting for the successful (OIDC) flows is not reported in all cases - I don't see it in my demos, but in any case, it makes sense to improve the way HTTP authorizer logs them. If it is an `AuthenticationFailedException` - report it means the challenge is required, and if it is `AuthenticationRedirectException` then report that it means the authentication is about to be completed (at that level we can't say `successful authentication` - while it is the case for OIDC, it might not be for some other cases)
- links to
-
RHSA-2023:124640 Red Hat build of Quarkus 3.2.9 release and security update