Hacker News Reader

I have worked with auth (:P) systems (IAM) a lot and I have never seen the problem with "auth" meaning both authorization and authentication. When more specificity is needed, just use the right phrase.

Using "login" and "permissions" are worse IMO, because they don't catch the entire meaning and complexity of these systems. Authentication means way more than login, and permissions mean very specific things for a small portion of an authorization system.

View on HN

Indeed, Authorization includes things like license checks, time of use restrictions, etc.

> Authorization includes things like license checks, time of use restrictions, etc.

permission to use X license... (or whatever license check means in this context)

permission to use at X time...

Of course, if you could just wave your magic wand and change the meaning of commonly understood words, you can make the semantics work. Unfortunately, you can't. In this case, "permission to use at X time" does not have the same meaning as "permission to perform action X".

I don't understand why would a magic wand or semantic gymnastics be required.

One can implement different kinds of permissions for a given resource. Including ones related to license or time constraints.

Reply on news.ycombinator.com