demo · v143

Config validator

Paste your .well-known/web-identity file. The page applies Chrome 143's new privacy rule: if the IdP config uses client_metadata_endpoint, the direct-endpoints format with both accounts_endpoint and login_url is required.

Pick a sample or paste your file.

checks

the rule

// v143 requires: if an IdP uses client_metadata_endpoint,
// .well-known/web-identity MUST use the direct-endpoints format with both:
//   "accounts_endpoint" and "login_url" explicitly listed.

// indirect (still allowed when NO client_metadata)
{ "provider_urls": ["https://idp.example/fedcm.json"] }

// direct (required when client_metadata_endpoint is configured)
{
  "accounts_endpoint": "https://idp.example/accounts",
  "login_url": "https://idp.example/login",
  "provider_urls": ["https://idp.example/fedcm.json"]
}

why this angle

The other concept simulates a fetch round trip; this one validates the file shape itself, which is what IdP operators need to ship before v143 lands. It's the exact check Chrome will perform.

see also