adeinega

8 ms·

1. 1.▲
   by adeinega 2y ago

   The beauty of this spec is that it defines a set of basic components to build multilateral federations between various types of entities (without a need to rely on Web PKI + of course, the types of these entities are limited by the imaginat
2. 2.▲
   by adeinega 2y ago

   I'd love to read about that more if you can share links explaining those details. Whatever you've described sounds more like internal problems / challenges of their own implementations than anything else... especially the Ope
3. 3.▲
   by adeinega 2y ago

   https://docs.aws.amazon.com/cognito/latest/developerguide/ex... tells me they support these IDPs 1. Facebook 2. Login with Amazon 3. Google 4. Sign in with Apple 5. Open ID Connect providers, and finally 6. S
4. 4.▲
   by adeinega 2y ago

   Where do they say that?
5. 5.▲
   by adeinega 2y ago

   "SAML isn't a recipient for innovations" or something along this line was once said by Vittorio Bertocci... it's hard to add much to it. OpenID Connect is a core for many new specs in the space, "OpenID for Verifiab
6. 6.▲
   by adeinega 2y ago

   I second this.
7. 7.▲
   by adeinega 2y ago

   Login.gov is pretty open about its preferences :) We strongly recommend choosing OpenID Connect (OIDC) over SAML due to its modern, API-centric design and support for native mobile applications. https://developers.login.gov/
8. 8.▲
   by adeinega 2y ago

   I hope there will be some changes on that soon, have a look at https://openid.net/specs/openid-federation-1_0.html .