New binary artifact management tool(github.com) |
New binary artifact management tool(github.com) |
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.
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.
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.
You can stash just about any binary, versioned, and control if it appears in your repo or just a little pointer file.
| 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.
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.
https://gist.github.com/HalCanary/9abb045bf047da118c2467266b...
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.