By Josh Cunningham

Sample Project

This tutorial shows you how to use the authorization features in the OAuth 2.0 framework to limit access to your or third-party applications.
For more information, read the API authorization documentation.

Create a Resource Server (API)

In the APIs section of the Auth0 dashboard, click Create API. Provide a name and an identifier for your API. You will use the identifier as an audience later, when you are configuring the Access Token verification. For Signing Algorithm, select RS256.

Add API Authorization

To restrict access to the resources served by your API, check the incoming requests for valid authorization information.
The authorization information is stored in the Access Token created for the user and needs to be sent in the Authorization header. To see if the token is valid, check it against the JSON Web Key Set (JWKS) for your Auth0 account. To learn more about validating Access Tokens, read the Verify Access Tokens tutorial.

This sample demonstrates how to check for a JWT in the Authorization header of an incoming HTTP request and verify that it is valid. The validity check is done in the JWTVerifier class from the auth0-PHP library which can be applied to any endpoints you wish to protect. If the token is valid, the resources which are served by the endpoint can be released, otherwise a 401 Authorization error will be returned.

Install the Dependencies

The auth0-PHP library and its JWTVerifier class can be used to verify incoming JWTs. The router library can be used to create simple routes. Install the libraries with composer.

composer require bramus/router:dev-master auth0/auth0-php:~5.0

Did it help?/

Configuration

By default, your API uses RS256 as the algorithm for signing tokens. Since RS256 uses a private/public keypair, it verifies the tokens against the public key for your Auth0 account. You can access this public key here.

We recommend using the default RS256 signing algorithm for your API. If you need to use the HS256 algorithm, see the HS256 integration sample.

Create an instance of JWTVerifier and pass your API identifier to valid_audiences and your Auth0 domain to authorized_iss. You can also create a function which will be called to return a message when a request is made to a protected endpoint.

With this configuration, any time an endpoint which includes /api/private is reached, a valid JWT access_token will be required before the resource can be released. With this in place, private routes can be defined.