4 ms·
It's here for Google https://accounts.google.com/.well-known/openid-configuration https://accounts.google.com/.well-known/openid-configuration Here for Microso
by tlarkworthy 4y ago
It's here for Google https://accounts.google.com/.well-known/openid-configuration https://accounts.google.com/.well-known/openid-configuration
Here for Microsoft https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration https://login.microsoftonline.com/common/v2.0/.well-known/op...
- BillinghamJ 4y agoAnd even for Apple: https://appleid.apple.com/.well-known/openid-configuration https://appleid.apple.com/.well-known/openid-configuration Facebook: https://www.facebook.com/.well-known/openid-configuration https://www.facebook.com/.well-known/openid-configuration
- kevincox 4y agoBut that's not the point. The goal of the discovery spec is that the user can enter an email and sign in with an OpenID connect provider of their choice. If I need to do an MX lookup and guess what identity provider they are using it doesn't solve the problem of needing to maintain a list of supported providers.
- tlarkworthy 4y agoTrue, the "well-known" path seems to be in a random location but maybe that's a problem with the spec, you might expect it to be off the root of the email domain.