Using OIDC Federation and FAPI together
@dpostnikov is already working on this.
Since Jul 11, 2026.
Assessment
This issue has not been assessed yet.
Description
Originally submitted by josephheenan (Joseph Heenan) on 2023-04-07
The Certification team have received several queries about using https://openid.net/specs/openid-connect-federation-1_0-17.html together with FAPI and whether any FAPI profile of Federation is necessary.
Possible items I noted that may require consideration:
- It may make sense to make a recommendation as to whether explicit or automatic client registration should/must be used
- The federation spec requires support for RS256, whereas FAPI has generally disallowed RS256 in favour of PS256.
but there may be further items.
Bitbucket status: open
Bitbucket origin: issue 595
- Dominant language
- HTML
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openid/fapi
-
component: FAPI 1: Advanced migrated-from-bitbucket priority: major type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
migrated-from-bitbucket priority: trivial type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
component: Certification component: FAPI2: Advanced Authorization
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
component: Certification component: FAPI2: Security Profile
Difficulty 4/5 3-5 days Newbie friendliness 35/100