Access token- A token used to access protected resources.Authorization code- An intermediary token generated when a user authorizes a client to access protected resources on their behalf. The client receives this token and exchanges it for an access token.Authorization server- A server which issues access tokens after successfully authenticating a client and resource owner, and authorizing the request.Client- An application which accesses protected resources on behalf of the resource owner (such as a user). The client could be hosted on a server, desktop, mobile or other device. See also Configuration/Client.Grant- A grant is a method of acquiring an access token. Also see the official documentation for common grant types.Resource server- A server which sits in front of protected resources (for example “tweets”, users’ photos, or personal data) and is capable of accepting and responding to protected resource requests using access tokens.Resource owner- The user who authorizes an application to access their account. The application’s access to the user’s account is limited to the “scope” of the authorization granted (e.g. read or write access).Scope- A permission.Tenant- The tenant serves as the top entity and is responsible for connecting users/apps to a backend service. A Tenant can be a company or a product with unique user group. It has Clients which represent different applications. See also Configuration/Tenant.JWT- A JSON Web Token is a method for representing claims securely between two parties as defined in RFC 7519.Provider- A provider are lightweight scripts that establish a seamless connection between Uitsmijter and a user data store
