Mobile + API: Solutions Overview
In order to ensure that only authorized users and applications are allowed access to the Timesheets API, ExampleCo has decided to make use of the OAuth 2.0 authorization framework. The framework provides the flexibility the company wants since the different grants can allow them to easily authorize the various types of application which need to communicate with the Timesheets API.
API Authentication and Authorization
An API is a way to expose functionality of your application to other applications. An application can make a request by sending a message to an endpoint on an API and receive information as a response.
An API endpoint can be secured or not. In our case, since the timesheets are sensitive information that affect reviews and payments, it is important to ensure that only authorized users and applications can call the endpoints on our API. When a client application wants to access protected endpoints on an API it needs to present an access token as proof that it has the required permissions for making the call to the endpoint.
An access token is obtained by authenticating the user with an Authorization Server and the user can then in turn authorize the application to access the API on their behalf.
What is an Access Token?
An access token (also referred to as
access_token) is an opaque string representing an authorization issued to the client. It may denote an identifier used to retrieve the authorization information or may self-contain the authorization information (for example, the user's identity, permissions, and so forth) in a verifiable manner.
It is quite common for access tokens to be implemented as JSON Web Tokens.
For more information on Auth0 Access Tokens refer to Access Token.
An API can enforce fine grained control over who can access the various endpoints exposed by the API. These permissions are expressed as scopes.
When a user authorizes a client application, the application can also indicate which permissions it requires. The user is then allowed to review and grant these permissions. These permissions are then included in the access token as part of the
Subsequently when the client passes along the access token when making requests to the API, the API can inspect the
scope claim to ensure that the required permissions were granted in order to call the particular API endpoint.
What are Scopes?
Each access token may include a list of the permissions that have been granted to the client. When a client authenticates with Auth0, it will specify the list of scopes (or permissions) it is requesting. If those scopes are authorized, then the access token will contain a list of authorized scopes.
For example, the timesheet API may accept four different levels of authorization: reading timesheets (scope
read:timesheets), creating timesheets (scope
create:timesheets), deleting timesheets (scope
delete:timesheets) and approving timesheets (scope
When a client asks the API to create a new timesheet entry, then the access token should contain the
create:timesheets scope. In a similar fashion, in order to delete existing timesheets, the access token should contain the
For more information on scopes refer to Scopes.
By using the OAuth 2.0 authorization framework, you can give your own applications or third-party applications limited access to your APIs on behalf of the application itself. Using Auth0, you can easily support different flows in your own APIs without worrying about the OAuth 2.0/OpenID Connect specification, or the many other technical aspects of API authorization.
In any OAuth 2.0 flow we can identify the following roles:
- Resource Owner: the entity that can grant access to a protected resource. Typically this is the end-user.
- Resource Server: the server hosting the protected resources. This is the API you want to access.
- Client: an application requesting access to a protected resource on behalf of the Resource Owner.
- Authorization Server: the server that authenticates the Resource Owner, and issues access tokens after getting proper authorization. In this case, Auth0.
Using different grants types (or flows), these participants will interact to grant to the client apps limited access to the APIs you are building. As a result, the client app will obtain an
access_token that can be used to call the API on behalf of the user.
Proof Key for Code Exchange (PKCE)
OAuth 2 provides several grant types for different use cases. In this particular use case, we want to access the API from a mobile application, which will use the OAuth 2.0 Proof Key for Code Exchange to do so.
The Authorization Code Grant has some security issues, when implemented on native applications. For instance, a malicious attacker can intercept the
authorization_code returned by Auth0 and exchange it for an Access Token (and possibly a Refresh Token).
The Proof Key for Code Exchange (PKCE) (defined in RFC 7636) is a technique used to mitigate this authorization code interception attack.
With PKCE, the Client creates, for every authorization request, a cryptographically random key called
code_verifier and its transformed value called
code_challenge, which is sent to Auth0 to get the
authorization_code. When the Client receives the
authorization_code, it will send the code and the
code_verifier to Auth0's token endpoint to exchange them for the requested tokens.
- The native app initiates the flow and redirects the user to Auth0 (specifically to the /authorize endpoint), sending the
- Auth0 redirects the user to the native app with an
authorization_codein the querystring.
- The native app sends the
code_verifiertogether with the
client_idto Auth0. This is done using the /oauth/token endpoint.
- Auth0 validates this information and returns an
access_token(and optionally a
- The native app can use the
access_tokento call the API on behalf of the user.
The Auth0 Authorization Extension allows you to provide authorization support in your application, by assigning Roles, Groups and Permissions to Users.
The Authorization Extension creates a Rule which will augment the User profile during the authentication flow with the Roles, Groups and Permissions assigned to the user. You can then use this information to ensure that the
access_token issued to a user only contains scopes which are allowed according to the permissions defined in the Authorization Extension.