Authority discovery draft.

discovery.md

Authority Discovery

To discover the authoritative Identity Provider for a given email address:

1. Extract the domain name from the email address and remember this as the Original Domain.

2. Using HTTPS, attempt to GET /.well-known/browserid from the Original Domain.

3. Depending on the response:

   a. If the document is absent, invalid, or explicitly disables BrowserID support, then the domain must not be considered authoritative. Clients may return to Step 2, substituting a Fallback Identity Provider for the Original Domain.

   b. If the document explicitly delegates to another domain, return to Step 2, substituting the delegated domain for the Original Domain.

   c. If the document is complete and valid, the discovered domain should be considered authoritative.

All requests for a /.well-known/browserid file must include a query parameter, domain, whose value is the domain initially derived in Step 1. This parameter may be omitted if and only if the value is identical to the domain being queried in Step 2.

Example: Direct support by the user's domain.

1. The user is [email protected], thus the Original Domain is example.com
2. GET https://example.com/.well-known/browserid?domain=example.com
3. The response is valid: example.com is authoritative for [email protected]

Example: Two levels of delegation by the user's domain.

1. The user is [email protected], thus the Original Domain is example.com
2. GET https://example.com/.well-known/browserid?domain=example.com
3. The response delegates to example.org
4. GET https://example.org/.well-known/browserid?domain=example.com
5. The response delegates to accounts.example.org
6. GET https://accounts.example.org/.well-known/browserid?domain=example.com
7. The response is valid: accounts.example.org is authoritative for [email protected]

Example: No direct support by the user's domain.

1. The user is [email protected], thus the Original Domain is example.com
2. GET https://example.com/.well-known/browserid?domain=example.com
3. The response is not a valid Support Document. Attempt discovery at against the fallback.test Fallback Identity Provider.
4. GET https://fallback.test/.well-known/browserid?domain=example.com
5. The response is valid: fallback.test is authoritative for [email protected]

The ?domain=example.com parameter could be omitted only in the second step of each example above. All subsequent steps would still require the ?domain=example.com parameter.