oskarstark / oauth2-php

The standard compliant OAuth2.0 library based on the Symfony Components.

AuthBucket\OAuth2

The primary goal of AuthBucket\OAuth2 is to develop a standards compliant RFC6749 OAuth2.0 library; secondary goal would be develop corresponding wrapper Symfony2 Bundle and Drupal module.

This library bundle with a Silex based AuthBucketOAuth2ServiceProvider for unit test and demo purpose. Installation and usage can refer as below.

Installation

Simply add a dependency on authbucket/oauth2-php to your project's composer.json file if you use Composer to manage the dependencies of your project.

Here is a minimal example of a composer.json:

{
    "require": {
        "authbucket/oauth2-php": "~2.4"
    }
}

Parameters

The bundled AuthBucketOAuth2ServiceProvider come with following parameters:

• authbucket_oauth2.model: (Optional) Override this with your own model classes, default with in-memory AccessToken for using resource firewall with remote debug endpoint.
• authbucket_oauth2.model_manager.factory: (Optional) Override this with your backend model managers, e.g. Doctrine ORM EntityRepository, default with in-memory implementation for using resource firewall with remote debug endpoint.
• authbucket_oauth2.user_provider: (Optional) For using grant_type = password, override this parameter with your own user provider, e.g. using InMemoryUserProvider or a Doctrine ORM EntityRepository that implements UserProviderInterface.

Services

The bundled AuthBucketOAuth2ServiceProvider come with following services controller which simplify the OAuth2.0 controller implementation overhead:

• authbucket_oauth2.oauth2_controller: OAuth2 endpoint controller.

Moreover, we also provide following model CRUD controller for alter raw data set:

• authbucket_oauth2.authorize_controller: Authorize endpoint controller.
• authbucket_oauth2.client_controller: Client endpoint controller.
• authbucket_oauth2.scope_controller: Scope endpoint controller.

Registering

If you are using Silex, register AuthBucketOAuth2ServiceProvider as below:

$app->register(new AuthBucket\OAuth2\Provider\AuthBucketOAuth2ServiceProvider());

Moreover, enable following service providers if that's not already the case:

$app->register(new Silex\Provider\SecurityServiceProvider());
$app->register(new Silex\Provider\SerializerServiceProvider());
$app->register(new Silex\Provider\ServiceControllerServiceProvider());
$app->register(new Silex\Provider\ValidatorServiceProvider());

Usage

This library seperate the endpoint logic in frontend firewall and backend controller point of view, so you will need to setup both for functioning.

To enable the built-in controller with corresponding routing, you need to mount it with a shared provider instance, all above controllers will be enabled accordingly with routing prefix /api/v1.0:

$provider = new AuthBucket\OAuth2\Provider\AuthBucketOAuth2ServiceProvider();
$app->register($provider);
$app->mount('/', $provider);

Below is a list of recipes that cover some common use cases.

Authorization Endpoint

We don't provide custom firewall for this endpoint, which you should protect it by yourself, authenticate and capture the user credential, e.g. by SecurityServiceProvider:

$app['security.encoder.digest'] = $app->share(function ($app) {
    return new PlaintextPasswordEncoder();
});

$app['security.user_provider.default'] = $app['security.user_provider.inmemory._proto'](array(
    'demousername1' => array('ROLE_USER', 'demopassword1'),
    'demousername2' => array('ROLE_USER', 'demopassword2'),
    'demousername3' => array('ROLE_USER', 'demopassword3'),
));

$app['security.firewalls'] = array(
    'oauth2_authorize' => array(
        'pattern' => '^/api/v1.0/oauth2/authorize$',
        'http' => true,
        'users' => $app['security.user_provider.default'],
    ),
);

Token Endpoint

Similar as authorization endpoint, we need to protect this endpoint with our custom firewall oauth2_token:

$app['security.firewalls'] = array(
    'oauth2_token' => array(
        'pattern' => '^/api/v1.0/oauth2/token$',
        'oauth2_token' => true,
    ),
);

Debug Endpoint

We should protect this endpoint with our custom firewall oauth2_resource:

$app['security.firewalls'] = array(
   'oauth2_debug' => array(
       'pattern' => '^/api/v1.0/oauth2/debug$',
       'oauth2_resource' => true,
   ),
);

Resource Endpoint

We don't provide other else resource endpoint controller implementation besides above debug endpoint. You should consider implement your own endpoint with custom logic, e.g. fetching user email address or profile image.

On the other hand, you can protect your resource server endpoint with our custom firewall oauth2_resource. Shorthand version (default assume resource server bundled with authorization server, query local model manager, without scope protection):

$app['security.firewalls'] = array(
    'resource' => array(
        'pattern' => '^/api/v1.0/resource',
        'oauth2_resource' => true,
    ),
);

Longhand version (assume resource server bundled with authorization server, query local model manager, protect with scope demoscope1):

$app['security.firewalls'] = array(
    'resource' => array(
        'pattern' => '^/api/v1.0/resource',
        'oauth2_resource' => array(
            'resource_type' => 'model',
            'scope' => array('demoscope1'),
        ),
    ),
);

If authorization server is hosting somewhere else, you can protect your local resource endpoint by query remote authorization server debug endpoint:

$app['security.firewalls'] = array(
    'resource' => array(
        'pattern' => '^/api/v1.0/resource',
        'oauth2_resource' => array(
        'resource_type' => 'debug_endpoint',
        'scope' => array('demoscope1'),
        'options' => array(
            'debug_endpoint' => 'http://example.com/api/v1.0/oauth2/debug',
            'cache' => true,
        ),
    ),
);

Demo

The demo is based on Silex and AuthBucketOAuth2ServiceProvider. Read though Demo for more information.

You may also run the demo locally. Open a console and execute the following command to install the latest version in the oauth2-php directory:

$ composer create-project authbucket/oauth2-php oauth2-php "~2.4"

Then use the PHP built-in web server to run the demo application:

$ cd oauth2-php
$ php app/console server:run

If you get the error There are no commands defined in the "server" namespace., then you are probably using PHP 5.3. That's ok! But the built-in web server is only available for PHP 5.4.0 or higher. If you have an older version of PHP or if you prefer a traditional web server such as Apache or Nginx, read the Configuring a web server article.

Open your browser and access the http://127.0.0.1:8000 URL to see the Welcome page of demo application.

Also access http://127.0.0.1:8000/admin/refresh_database to initialize the bundled SQLite database with user account admin:secrete.

Documentation

OAuth2's documentation is built with Sami and publicly hosted on GitHub Pages.

To built the documents locally, execute the following command:

$ vendor/bin/sami.php update .sami.php

Open build/sami/index.html with your browser for the documents.

Tests

This project is coverage with PHPUnit test cases; CI result can be found from Travis CI; code coverage report can be found from Coveralls.

To run the test suite locally, execute the following command:

$ vendor/bin/phpunit

Open build/logs/html with your browser for the coverage report.

References

• RFC6749
• Demo
• API
• GitHub
• Packagist
• Travis CI
• Coveralls

License

• Code released under MIT
• Docs released under CC BY-NC-SA 3.0