meaning of FAPI2 requirements around publishing discovery data

Open
#862 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Domain
documentation, testing

Research direction

Start by comparing the quoted FAPI2 requirement with the OIDD and RFC8414 references, then inspect the conformance tests described in the issue: OpenID configuration is checked when OIDC is enabled, and OAuth authorization-server metadata otherwise. Done means the WG clarifies whether both metadata documents are required and the tests reflect that decision.

Written by the indexing model from the issue text.

Description

component: Certification component: FAPI2: Security Profile

What does the 'and' here mean:

shall distribute discovery metadata (such as the authorization endpoint) via the metadata document as specified in [OIDD] and [RFC8414];

Does it mean a server has to publish both?

Currently the conformance tests check:

  1. if openid connect is enabled, only openid-configuration is checked
  2. if openid connect is not enabled, only oauth-authorization-server is checked

Given the 'and' I'm not actually sure this is correct and if server's are expected to publish in both locations?

Discussed a bit on today's WG call.

Dominant language
HTML
Stars
4
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openid/fapi

All issues in openid/fapi

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.