Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 64 commits ahead, 20 commits behind kivra:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

P1 OAuth2

CI Coverage Status Hex version

This library is designed to simplify the implementation of the server side of OAuth2 ( It provides no support for developing clients. See oauth2_client for support in accessing Oauth2 enabled services.

oauth2 is released under the terms of the MIT license

Current stable version: 0.6.0

Current α alpha version: 0.6.x

copyright 2012-2014 Kivra



Check out the examples.

Related projects

Webmachine server implementation by Oauth2 contributor Ivan Martinez: oauth2_webmachine.

Redis backed Oauth2 backend.



A token is a (randomly generated) string provided to the client by the server in response to some form of authorization request. There are several types of tokens:

  • Access Token: An access token identifies the origin of a request for a privileged resource.
  • Refresh Token: A refresh token can be used to replace an expired access token.


Access tokens can (optionally) be set to expire after a certain amount of time. An expired token cannot be used to gain access to resources.


A token is associated with an identity -- a value that uniquely identifies a user, client or agent within your system. Typically, this is a user identifier.


The scope is handled by the backend implementation. The specification outlines that the scope is a space delimetered set of parameters. This library has been developed with the following in mind.

Scope is implemented as a set and loosely modeled after the Solaris RBAC priviliges, i.e. solaris.x.* and implemented as a MAC with the ability to narrow the scope but not extend it beyond the predefined scope.

But since the scope is opaque to this Oauth2 implementation you can use the scoping strategy that best suit your workflow.

There is a utility module to work with scope. The recommendation is to pass a Scope as a list of binaries, i.e. [<<"root.a.c.b">>, <<"root.x.y.z">>] you can then validate these against another set like:

> oauth2_priv_set:is_subset(oauth2_priv_set:new([<<"root.a.b">>, <<"root.x.y">>]),
> oauth2_priv_set:is_subset(oauth2_priv_set:new([<<"root.a.b">>, <<"root.x.y">>]),
> oauth2_priv_set:is_subset(oauth2_priv_set:new([<<"root.a.b">>, <<"root.x.y">>]),
                            oauth2_priv_set:new([<<"root.a.*">>, <<"root.x.y">>])).


If you have many diverse clients connecting to your service -- for instance, a web client and an iPhone app -- it's desirable to be able to distinguish them from one another and to be able to grant or revoke privileges based on the type the client issuing a request. As described in the OAuth2 specification, clients come in two flavors:

  • Confidential clients, which can be expected to keep their credentials from being disclosed. For instance, a web site owned and operated by you could be regarded as confidential.
  • Public clients, whose credentials are assumed to be compromised the moment the client software is released to the public.

Clients are distinguished by their identifiers, and can (optionally) be authenticated using a secret key shared between the client and server.


If you want to run the EUnit test cases, you can do so with:

$ make ct


The library makes no assumptions as to how you want to implement authentication and persistence of users, clients and tokens. Instead, it provides a behavior (oauth2_backend) with functions that needs to be implemented. To direct calls to a different backend module, simply set {backend, your_backend_module} in the oauth2 section of your app.config.

Look at oauth2_mock_backend for how a backend can be implemented.

The following example demonstrates a basic app.config section for oauth2.

    {oauth2, [
        %% Default expiry_time for access_tokens unless
        %% overridden per flow
        {expiry_time, 3600}
        ,{backend, backend_goes_here}

        %% Optional expiry_time override per flow
        ,{password_credentials, [
            {expiry_time, 7200}
        ,{client_credentials, [
            {expiry_time, 86400}
        ,{refresh_token, [
            {expiry_time, 2592000} %% 30 Days
        ,{code_grant, [
            %% Recommended absolute expiry time from the spec
            {expiry_time, 600}

A complete list of functions that your backend must provide is available by looking at oauth2_backend.erl, which contains documentation and function specifications.

To implement a custom token generation backend you can change your app.config as such:

    {oauth2, [
        {token_generation, YOUR_TOKEN_GENERATOR}

The default token generator is called oauth2_token. To implement your own you should create your own module implementing the oauth2_token_generation behavior exporting one function generate/0.


Erlang Oauth2 implementation








No packages published


  • Erlang 99.6%
  • Makefile 0.4%