fapi

Implementing Financial-grade API (FAPI) security profiles requires enforcing baseline and advanced verification rules across OAuth and OpenID Connect flows. This Skill provides architectural guidance, example verifiers, and module references to secure IdP-server integrations.

FAPI Baseline and FAPI Advanced compliance requirements differ by the strictness of their security verifiers. This Skill provides guidance covering both profiles, enforcing concrete technical requirements for secure, standards-compliant OAuth and OIDC behavior.

Configuring mTLS client authentication for secure API access workflows involves applying specific FAPI configuration patterns across your libraries and extensions. This Skill provides documented module structures and verifiers to validate mTLS implementation.

Setting up Pushed Authorization Requests (PAR) and JARM for enterprise IdP integrations requires following specific FAPI architectural patterns. This Skill provides practical examples and configuration guidance to implement and test these flows.

Yes, this guidance supports multi-tenant configurations for FAPI-CIBA flows. It provides architectural patterns and configuration guidance applicable across enterprise IdP-server integrations requiring FAPI compliance.

Validating FAPI features across existing libraries and extensions is limited by the need to enforce concrete technical requirements through documented module structures. This Skill focuses on FAPI baseline, advanced, CIBA, PAR, JARM, and mTLS validation rules.