3 ms·
For this purpose, I'd strongly prefer LDAP over OIDC. The reason being, companies that have a need for something like this are much more likely to be set up wi
by mumblemumble 6y ago
For this purpose, I'd strongly prefer LDAP over OIDC.
The reason being, companies that have a need for something like this are much more likely to be set up with their own LDAP server than with their own OIDC provider. I'm guessing the next most useful one might (still) be SAML, and then OIDC would be the cherry on top.
- l3s2d 6y agoI think OIDC should be the default authentication for services like this. It is the newest, and simplest, of the three. Any sort of integration with existing SAML or LDAP can be done via a bridge. Keycloak supports this, I believe.
- user5994461 6y agoIndeed OIDC is the standard nowadays and for the future years. Active Directory has OIDC support since version 2016 (and SAML since earlier), which makes it the de facto supported protocol in companies. SAML is rightfully losing adoption because it's way more difficult to use. LDAP is moot for a variety of reasons, though it's still used by some internal services.
- thinkmassive 6y agoIf you visit the issue I linked you’ll see they crossed out SAML support with the note “won't be implemented, since repository authentication mechanisms doesn't support these providers”
- closeparen 6y agoLDAP pins you down to a username+password flow and requires you to handle that password. Would much rather see authentication flows that are ready for WebAuthN, etc. by default.
- mumblemumble 6y ago100% agreed there. I'm just thinking, you generally get more value out of building for the world you live in than out of building for the world you wish you lived in.