4 ms·
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
by chromatin 5y ago
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 https://kanidm.github.io/kanidm/intro.html
- sigg3 5y agoauth is auth. Don't overcomplicate the matter.
- politician 5y agoAuthentication and Authorization are distinct concepts whose English terms both start with the same prefix.
- nick__m 5y agoThe set of possible Authorization policies without having some form of Authentication is quite limited ;)
- politician 5y agoWithin ABAC schemes, Authorization is a boolean function over (Request, Principle, Environment). If you zero the Principle, you can still represent a large number of unique policies considering just the Request and the Environment.
- krono 5y agoYou 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?
- b0afc375b5 5y agoAuthentication - can you login or not? Authorization - should you be able to see the admin dashboard or not?
- yaleman 5y agoAuthentication is part of the "accounts" part. :)
- firstyear 5y agoJust for you, I fixed up this line in the book to make it clearer. Issue reports about things like this is docs and clarity are always welcome!