Incorrect documentation for Direct Naked Impersonation Configuration
#35.902 aberto em 13 de dez. de 2024
Métricas do repositório
- Stars
- (34.398 estrelas)
- Métricas de merge de PR
- (Métricas PR pendentes)
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
docs
Describe the bug
In the documentation for the Direct Naked Impersonation it is shown that the Client Policy must be added to the user-impersonated permission (containing the user-impersonated scope) which does not work and results in an error - Client not allowed to exchange.
Upon testing with the client policy applied to the admin-impersonating permission, it works.
It would be great if we can fix this as there are some threads on stackoverflow about this, too. Also, it would be great if we can include a little more information about the difference between the two permissions (and scopes).
https://www.keycloak.org/securing-apps/token-exchange#_direct_naked_impersonation
Version
26.0.7
Regression
- The issue is a regression
Expected behavior
Correct configurations for both permissions.
Actual behavior
Incorrect configurations for both permissions.
How to Reproduce?
N/A
Anything else?
No response