Documentation about Australia Consumer Data Right security profile

[tnorimat]

Description

Documentation about Australia Consumer Data Right security profile can be added to the page about FAPI support.

Discussion

No response

Motivation

The reason is as follows.

• Keycloak 15 supported only the former and passed its conformance tests. Keycloak did not support the latter.
  https://github.com/keycloak/kc-sig-fapi#australia-consumer-data-right-cdr

• Also, Keycloak got certified as FAPI OP - Australia CDR by OpenID Foundation.
  https://openid.net/certification/

Considering the points above, it might be better to write that Keycloak is compliant with Australia Consumer Data Right security profile.

Details

For example,

==== Australia Consumer Data Right (CDR) Security Profile

{project_name} is compliant with the https://consumerdatastandardsaustralia.github.io/standards/#security-profile[Australia Consumer Data Right Security Profile].

If you want to apply Australia CDR security profile, you need to use `fapi-1-advanced` profile because Australia CDR security profile is based on FAPI 1.0 Advanced security profile. If your client also applies PAR, make sure that it applies RFC 7637 Proof Key for Code Exchange (PKCE) because Australia CDR security profile requires to apply PKCE when applying PAR. This can be achieved by using a client profile with the `pkce-enforcer` executor.