alf-auth0 0.8.1

OAuth Client adapted to work with Auth0

alf-auth0 ===

Python OAuth 2 Client

alf is an OAuth 2 Client based on requests.Session with seamless support for the Client Credentials Flow.

Features

• Automatic token retrieving and renewing

• Token expiration control

• Automatic token storage

• Automatic retry on status 401 (UNAUTHORIZED)

• Works with Auth0 Client Credentials Flow

Usage

Initialize the client and use it as a requests.Session object.

from alf.client import Client

alf = Client(
    token_endpoint='http://example.com/token',
    client_id='client-id',
    client_secret='secret')

resource_uri = 'http://example.com/resource'

alf.put(
    resource_uri, data='{"name": "alf"}',
    headers={'Content-Type': 'application/json'})

alf.get(resource_uri)

alf.delete(resource_uri)

Using your custom token storage

Now passing an object with get and set attributes you can store or retrieve a token.

This object can be a Redis, Memcache or your custom object.

from alf.client import Client
from redis import StrictRedis

redis = StrictRedis(host='localhost', port=6379, db=0)

alf = Client(
    token_endpoint='http://example.com/token',
    client_id='client-id',
    client_secret='secret',
    token_storage=redis)

resource_uri = 'http://example.com/resource'

alf.put(
    resource_uri, data='{"name": "alf"}',
    headers={'Content-Type': 'application/json'})

alf.get(resource_uri)

alf.delete(resource_uri)

Using alf with Auth0

For the Client to work with Auth0 you need to initialize it with audience and token_default_expire_in.

Auth0 is not returning expires_in when you call authentication endpoint. As a result you should set token_default_expire_in as the same value (or a bit smaller, to be safe) that you have set it in Auth0 management console > APIs > <your_api_name> > Settings > Token Expiration (Seconds) field

Audience should be set as your API Identifier in Auth0.

from alf.client import Client

alf = Client(
    token_endpoint='http://example.com/token',
    audience='http://api.example.com/my-api/',
    token_default_expire_in=86400
    client_id='client-id',
    client_secret='secret')

resource_uri = 'http://example.com/resource'

How does it work?

Before the request, a token will be requested on the authentication endpoint and a JSON response with the access_token and expires_in keys will be expected.

Multiple attempts will be issued after an error response from the endpoint if the token_retries argument is used. Check token-retrying for more info.

alf keeps the token until it is expired according to the expires_in value.

The token will be used on a Bearer authorization header for the original request.

GET /resource/1 HTTP/1.1
Host: example.com
Authorization: Bearer token-12312

If the request fails with a 401 (UNAUTHORIZED) status, a new token is retrieved from the endpoint and the request is retried. This happens only once, if it fails again the error response is returned.

The token will be reused for every following request until it is expired.

Token Retrying

The client supports the retry interface from urllib3 to repeat attempts to retrieve the token from the endpoint.

The following code will retry the token request 5 times when the response status is 500 and it will wait 0.3 seconds longer after each error (known as backoff).

from requests.packages.urllib3.util import Retry
from alf.client import Client

alf = Client(
    token_endpoint='http://example.com/token',
    client_id='client-id',
    client_secret='secret',
    token_retry=Retry(total=5, status_forcelist=[500], backoff_factor=0.3))

Workflow

Troubleshooting

In case of an error retrieving a token, the error response will be returned, the real request won’t happen.

Related projects

djalf

An extended client that uses Django’s cache backend to share tokens between server instances.

tornado-alf

A port of the alf client using tornado’s AsyncHTTPClient.