31–40 of 56 posts
Earlier quoted context omitted.
auth is auth. Don't overcomplicate the matter.
Authentication and Authorization are distinct concepts whose English terms both start with the same prefix.
Earlier quoted context omitted.
Looks like it squarely competes with FreeIPA. Maybe main differentiator is that FreIPA is in python whereas this is in rust (and so less prone to bugs)?
Is it a widely held concept that Rust is less prone to bugs compared to Python? I've only heard it being compared to C, and only wrt. memory safety bugs.
Earlier quoted context omitted.
auth is auth. Don't overcomplicate the matter.
You would be the one overcomplicating the matter by clumping these distinct concepts together. Edit: For those unfamiliar with the concepts: Authentication: subject identity - is the user who they claim to be? Authorization: subject permissions - is this user permitted to execute that action?
Authorization - should you be able to see the admin dashboard or not?
Nobody is mentioning a big open source project like Grouper, https://incommon.org/trusted-access/ Can someone tell me why is this project, or 4 softwares, not more widely known?
Grouper look promising but there are performance problems with Grouper when you reach a certain scale. When I tried to import my institution LDAP, I had to exclude the major groups it was meant to manage as they were basically undeletable. Sure you could easily delete one reference group ex (u:ref:students:adm:adm101:20201:01) but deleting all the group from a faculty (evrything under u:ref:students:adm) took more th…
In my institution I have to replace a long lived solution that even suports a nis domain, and I feel a bit overwhelmed.
Trying to read the docs and look through the code, and it all seems very jumbled, like someone had ADHD and went around implementing a dozen different things that relate to identity and authZ. It would seem like the efforts might be best applied as independent components that combine with other open source solutions, to prevent reinventing the wheel, and create more independent composeable solutions that do one thing…
Earlier quoted context omitted.
Well, objectively, looking at that page or for example the grouper page ( https://incommon.org/software/grouper/ ) I fail to get /exactly/ where grouper fits in, what it does and doesn’t do, and just generally why I would or wouldn’t choose it in my application. Likely, busy people don’t spend a lot of time digging in to software that doesn’t effectively communicate clearly what it is, unless they know from a trusted…
I would have thought that in SCIM provisioning people would invest more time researching for existing projects. Said that, I fully understand why people would not invest enough time to understand the Grouper environment, I going through it and feels like a punishment. If someone wants to see the potential, check this list of known users and their use cases : https://spaces.at.internet2.edu/display/Grouper/Community+C…
I like these types of projects (auth) and happy to see this is a thriving area. I was a little puzzled by the very first line in their gitbook [0] documentation: “Kanidm is an identity management server, acting as an authority on accounts and authorisation within a technical environment.” Shouldn’t that be authentication, or am I misunderstanding the purpose of Kanidm? [0] https://kanidm.github.io/kanidm/intro.html