mirror of
https://github.com/keycloak/keycloak.git
synced 2025-12-21 06:20:05 -06:00
Documentation Inconsistency about Open Banking(Finance) Brasil FAPI security profile (#25163)
closes #25108
Signed-off-by: Takashi Norimatsu <takashi.norimatsu.ws@hitachi.com>
(cherry picked from commit 29aec9c5b5)
Co-authored-by: Takashi Norimatsu <takashi.norimatsu.ws@hitachi.com>
This commit is contained in:
committed by
GitHub
parent
3fd24dc2d1
commit
87542596e1
@@ -25,9 +25,9 @@ In case you want to use <<_backchannel_authentication_endpoint,CIBA>> in a FAPI
|
||||
There is a need to use the `fapi-1-advanced` profile, or other client profile containing the requested executors, as the `fapi-ciba` profile contains just CIBA-specific executors.
|
||||
When enforcing the requirements of the FAPI CIBA specification, there is a need for more requirements, such as enforcement of confidential clients or certificate-bound access tokens.
|
||||
|
||||
==== Open Banking Brasil Financial-grade API Security Profile
|
||||
==== Open Finance Brasil Financial-grade API Security Profile
|
||||
|
||||
{project_name} is compliant with the https://openbanking-brasil.github.io/specs-seguranca/open-banking-brasil-dynamic-client-registration-1_ID2-ptbr.html[Open Banking Brasil Financial-grade API Security Profile 1.0 Implementers Draft 2].
|
||||
{project_name} is compliant with the https://openfinancebrasil.atlassian.net/wiki/spaces/OF/pages/82083996/EN+Open+Finance+Brasil+Financial-grade+API+Security+Profile+1.0+Implementers+Draft+3[Open Finance Brasil Financial-grade API Security Profile 1.0 Implementers Draft 3].
|
||||
This one is stricter in some requirements than the <<_fapi-support,FAPI 1 Advanced>> specification and hence it may be needed to configure link:{adminguide_link}#_client_policies[Client Policies]
|
||||
in the more strict way to enforce some of the requirements. Especially:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user