-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
False
-
None
-
False
-
+
-
---
-
-
It follows #36459 (which in itself was correct but not complete), this time with a proper test, where both client name and now the token exchange requirement being customized at the custom filter level as opposed to in the properties.
Both `oidc-token-propagation/deployment` and `oidc-token-propagation-reactive/deployment` already test the exchange requirement configured in the properties.
Relates to #36440 and #36458.
- links to
-
RHSA-2023:124640 Red Hat build of Quarkus 3.2.9 release and security update