New binary artifact management tool

Post by thinkmassive » Fri, Nov 20, 2020, 4:16 PM UTC

mumblemumble wrote: post #9

l3s2d wrote: post #5

Earlier quoted context omitted.

General observation, not necessarily related to this project: It's rather unfortunate that federated identity is always an afterthought instead of the default. Every new project could have been using OpenID Connect instead of rolling their own authentication. I really wish web frameworks pushed for this. I suppose some of the blame lies with the identity providers. So many of them use a custom OAuth protocol instead…

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.

Post by user5994461 » Fri, Nov 20, 2020, 6:10 PM UTC

l3s2d wrote: post #10

mumblemumble wrote: post #9

Earlier quoted context omitted.

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.

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.

Post by Karliss » Fri, Nov 20, 2020, 7:45 PM UTC

varikin wrote: post #14

It says both: | It can host the data in the file system, Amazon S3, Google Cloud, HuaweiCloud OBS etc. and | For now, we support two storage types: file system and S3 storages. Along with lack of LDAP or federated login, it doesn't seem ready to try or recommend yet.

Post by dividedbyzero » Fri, Nov 20, 2020, 9:30 PM UTC

Karliss wrote: post #15

varikin wrote: post #14

It says both: | It can host the data in the file system, Amazon S3, Google Cloud, HuaweiCloud OBS etc. and | For now, we support two storage types: file system and S3 storages. Along with lack of LDAP or federated login, it doesn't seem ready to try or recommend yet.

Can't the storage thing be explained by other cloud providers having storage solutions that are compatible with Amazon S3 API?

Post by closeparen » Fri, Nov 20, 2020, 9:34 PM UTC

mumblemumble wrote: post #9

l3s2d wrote: post #5

Earlier quoted context omitted.

General observation, not necessarily related to this project: It's rather unfortunate that federated identity is always an afterthought instead of the default. Every new project could have been using OpenID Connect instead of rolling their own authentication. I really wish web frameworks pushed for this. I suppose some of the blame lies with the identity providers. So many of them use a custom OAuth protocol instead…

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.