AbsoluteJS

OpenID Conformance Suite

conformance-suiteworkspacealphaDev Tools

This is the OpenID Foundation conformance suite, which covers OpenID Connect, FAPI1-Advanced, FAPI2, FAPI-CIBA and OpenID for Identity Assurance (ekyc).

#Installation

BASH
git clone https://gitlab.com/openid/conformance-suite.git

#Capabilities

Repository composition

0 public packages and 1 private workspace project are versioned and developed together.

Overview

This is the OpenID Foundation conformance suite, which covers OpenID Connect, FAPI1-Advanced, FAPI2, FAPI-CIBA and OpenID for Identity Assurance (ekyc).

The project is located at https://gitlab.com/openid/conformance-suite and all issues / merge requests should be submitted there.

See the wiki for more info: https://gitlab.com/openid/conformance-suite/wikis/home

Show 10 more

For user instructions for testing / certifying please see:

https://openid.net/certification/instructions/

To get started as a developer or running the conformance suite locally, see:

https://gitlab.com/openid/conformance-suite/wikis/Developers/Build-&-Run

For guidelines for submitting contributions, see:

https://gitlab.com/openid/conformance-suite/wikis/Developers/Contributing

OpenID Foundation would like to thank the follow people/organisations:

OpenBanking Ltd, for donating the FAPI conformance suite that formed

the basis of this code

Office of the National Coordinator for Health Information

Outcomes

What you can build

Build on the supported package contract

Use conformance-suite through its supported public entry points.

Hardening checklist

Production guidance

Make every external boundary explicitPin the deployed conformance-suite version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.

Follow in order

Troubleshooting path

1
Trace from the first failed boundary
Reproduce the smallest canonical conformance-suite example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.

#Workspace contents

0 public packages and 1 private workspace project are maintained in this repository.

Workspace project
This workspace project is not published as a standalone npm package. Use its repository and the accurately labeled public or private workspace contents below.