From 41059fad9b047ac320dc1f76c83fefe4bb5cc72f Mon Sep 17 00:00:00 2001 From: Aaron Parecki Date: Wed, 14 Feb 2024 15:23:34 -0800 Subject: [PATCH 1/2] clarify client_metadata It was not clear on first reading why the IdP is providing RP metadata. Hopefully this text helps provide clues to the reader earlier on. --- files/en-us/web/api/fedcm_api/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/files/en-us/web/api/fedcm_api/index.md b/files/en-us/web/api/fedcm_api/index.md index 2b9a404e0844070..5b78194a812b1db 100644 --- a/files/en-us/web/api/fedcm_api/index.md +++ b/files/en-us/web/api/fedcm_api/index.md @@ -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}} @@ -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: ```json { From 23091f7450953d93806fb9e9cb660ece8f6abd03 Mon Sep 17 00:00:00 2001 From: sideshowbarker Date: Thu, 15 Feb 2024 12:06:01 +0900 Subject: [PATCH 2/2] Update files/en-us/web/api/fedcm_api/index.md --- files/en-us/web/api/fedcm_api/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/fedcm_api/index.md b/files/en-us/web/api/fedcm_api/index.md index 5b78194a812b1db..0154b54d34263bc 100644 --- a/files/en-us/web/api/fedcm_api/index.md +++ b/files/en-us/web/api/fedcm_api/index.md @@ -136,7 +136,7 @@ This includes the following information: #### The client metadata endpoint -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: +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: ```json {