Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New binary artifact management tool

github.com

Post reply on HN
Print view View original

1–10 of 22 posts

Re: New binary artifact management tool

#3

Post by thinkmassive »

To replace Artifactory, Nexus, etc (as claimed at the start of the readme) authentication is an important component.

Right now Artipie appears to support credentials stored in a flat file, or integration with GitHub. There’s an open issue[0] that makes it sound like LDAP integration is in progress, but the only comment of substance is “you should donate to make this happen faster.”

That’s somewhat unfortunate, because it’d be nice to have some idea of the current progress on the issue beforehand.

[0] https://github.com/artipie/artipie/issues/24

Re: New binary artifact management tool

#5

Post by l3s2d »

thinkmassive wrote: post #3

To replace Artifactory, Nexus, etc (as claimed at the start of the readme) authentication is an important component. Right now Artipie appears to support credentials stored in a flat file, or integration with GitHub. There’s an open issue[0] that makes it sound like LDAP integration is in progress, but the only comment of substance is “you should donate to make this happen faster.” That’s somewhat unfortunate, becaus…

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 of OIDC, which shifts the burden to the developers. Adding a new IdP should be as simple as adding a new trusted URL, instead it's often integrating a new SDK.

Re: New binary artifact management tool

#8

Post by eternalban »

debarshri wrote: post #2

I wonder if "Java code is extraordinary high" can be the moat for a company.

You made me grep for that in the OP.

They are claiming "quality of Java code is extraordinary high". It is not even merely "good": Here is looking at you, dear misnamed and all over the place "Slice" flavors.

Re: New binary artifact management tool

#9

Post by mumblemumble »

l3s2d wrote: post #5
thinkmassive wrote: post #3

To replace Artifactory, Nexus, etc (as claimed at the start of the readme) authentication is an important component. Right now Artipie appears to support credentials stored in a flat file, or integration with GitHub. There’s an open issue[0] that makes it sound like LDAP integration is in progress, but the only comment of substance is “you should donate to make this happen faster.” That’s somewhat unfortunate, becaus…

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.

Re: New binary artifact management tool

#10

Post by l3s2d »

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.

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 reply on HN