Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clarify client_metadata #32287

Merged
merged 2 commits into from
Feb 15, 2024
Merged

clarify client_metadata #32287

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41059fa
clarify client_metadata
aaronpk Feb 14, 2024
23091f7
Update files/en-us/web/api/fedcm_api/index.md
sideshowbarker Feb 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions files/en-us/web/api/fedcm_api/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ The properties are as follows:
- `accounts_endpoint`
- : The URL for the accounts list endpoint, which returns a list of accounts that the user is currently signed in to on the IdP. The browser uses these to create a list of sign-in choices to show to the user in the browser-provided FedCM UI.
- `client_metadata_endpoint` {{optional_inline}}
- : The URL for the client metadata endpoint, which provides URLs pointing to the RP's metadata and terms of service pages, to be used in the FedCM UI.
- : The URL for the client metadata endpoint, which provides URLs pointing to the RP's metadata and terms of service pages as registered at the IdP, to be used in the FedCM UI.
- `id_assertion_endpoint`
- : The URL for the ID assertion endpoint, which when sent valid user credentials should respond with a validation token that the RP can use to validate the authentication.
- `branding` {{optional_inline}}
Expand Down Expand Up @@ -136,7 +136,7 @@ This includes the following information:

#### The client metadata endpoint

Provides URLs pointing to the RP's metadata and terms of service pages, to be used in the browser-supplied FedCM UI. This should follow the JSON structure seen below:
An endpoint at the IdP that takes a client_id as input and provides URLs pointing to the RP's metadata and terms of service pages, to be used in the browser-supplied FedCM UI. This should follow the JSON structure seen below:
sideshowbarker marked this conversation as resolved.
Show resolved Hide resolved

```json
{
Expand Down
Loading