I 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.
Re:New binary artifact management tool
by user5994461 on Friday November 20, 2020 @01:10PM
(#25163127)
Indeed 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.
Re:New binary artifact management tool
by closeparen on Friday November 20, 2020 @04:34PM
(#25165288)
LDAP 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.
Re:New binary artifact management tool
by mumblemumble on Friday November 20, 2020 @06:30PM
(#25166408)
100% 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.
Re:New binary artifact management tool
by thinkmassive on Friday November 20, 2020 @11:16AM
(#25161810)
If 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”
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.