Authored by Andreas Helland
Pro tip: Authentication (AuthN) is about answering the question "who are you?". Authorization (AuthZ) follows, and is about answering the question "should you be allowed to access this resource?".
Pro tip: For an interactive login by an end-user OpenID Connect is usually what you want. For a server type non-interactive login OAuth is what you want.
Pro tip: if an end user has direct access to the executable the client is considered untrusted - aka unable to keep secrets.
Pro tip: Follow these general designations, and think twice before implementing "clever" variants of these.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.