Standards - SecureApiGateway/SecureApiGateway GitHub Wiki

The Secure API Gateway (SAPI-G) is built on a number of different standards to ensure compliance.

Open Banking Standard

The key one is the Open Banking Standard.

The Secure Banking specifications have been created by the Open Banking Implementation Entity and is UK specific. ForgeRock has developed SAPI-G to provide a core set of tools that can be used to protect any API using the security profiles adopted by the Open Banking specifications. This allows SAPI-G to be used to protect a variety of banking and other industry data access APIs such as the Berlin Group specifications, the Consumer Data Right (CDR) and so on.

OAuth 2.0 and OpenID Connect (OIDC) Standards

See Open Banking for a good overview of how Open Banking uses OAuth 2.0 and OIDC, along with Financial-grade API (FAPI) and Client-Initiated Backchannel Authentication (CIBA).

OAuth 2.0

OIDC