FAPI 2.0 Security Profile Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions · Issue #41119 · keycloak/keycloak · GitHub
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
{{ message }}
Repository navigation
FAPI 2.0 Security Profile Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions #41119
On receiving a client authentication assertion from a client, Keycloak only accept its issuer identifier value as a string in the aud claim received in the client authentication assertion.
the issuer value is equal to the issuer claim value of the server metadata that the client can obtain by accessing well-known URI.
Discussion
No response
Motivation
Making Keycloak fully comply with FAPI 2.0 Security Profile Final specification.
changed the title [-]FAPI 2.0 Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions[/-][+]FAPI 2.0 Security Profile Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions[/+]on Jul 22, 2025
Activity
FAPI 2.0 Final - only accept its issuer identifier value as a string …
[-]FAPI 2.0 Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions[/-][+]FAPI 2.0 Security Profile Final - only accept its issuer identifier value as a string in the aud claim received in client authentication assertions[/+]