AuthBucket\Bundle\OAuth2Bundle is a Symfony Bundle, which integrate AuthBucket\OAuth2 as easy as possible into your Symfony Project.
Simply add a dependency on authbucket/oauth2-symfony-bundle 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-symfony-bundle": "~5.0"
}
}
This bundle come with following parameters:
model: (Optional) Override this with your own model classes, default with in-memory AccessToken for using resource firewall with remote debug endpoint.driver: (Optional) Currently we support in-memory (in_memory), or Doctrine ORM (orm). Default with in-memory for using resource firewall with remote debug endpoint.user_provider: (Optional) For usinggrant_type = password, override this parameter with your own user provider, e.g. using InMemoryUserProvider or a Doctrine ORM EntityRepository that implements UserProviderInterface.
This bundle come with following services controller which simplify the OAuth2.0 controller implementation overhead:
authbucket_oauth2.authorization_controller: Authorization Endpoint controller.authbucket_oauth2.token_controller: Token Endpoint controller.authbucket_oauth2.debug_controller: Debug Endpoint controller.
You have to add AuthBucketOAuth2Bundle to your AppKernel.php:
# app/AppKernel.php
class AppKernel extends Kernel
{
public function registerBundles()
{
$bundles = [
new AuthBucket\Bundle\OAuth2Bundle\AuthBucketOAuth2Bundle(),
];
return $bundles;
}
}
Moreover, enable following bundles if that's not already the case:
$bundles = [
new Symfony\Bundle\FrameworkBundle\FrameworkBundle(),
new Symfony\Bundle\SecurityBundle\SecurityBundle(),
new Symfony\Bundle\MonologBundle\MonologBundle(),
];
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, add the following into your routing.yml, all above controllers will be enabled accordingly with routing prefix /api/oauth2:
# app/config/routing.yml
authbucketoauth2bundle:
prefix: /api/oauth2
resource: "@AuthBucketOAuth2Bundle/Resources/config/routing.yml"
Below is a list of recipes that cover some common use cases.
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 SecurityBundle:
# app/config/security.yml
security:
encoders:
Symfony\Component\Security\Core\User\User: plaintext
providers:
default:
memory:
users:
demousername1: { roles: 'ROLE_USER', password: demopassword1 }
demousername2: { roles: 'ROLE_USER', password: demopassword2 }
demousername3: { roles: 'ROLE_USER', password: demopassword3 }
firewalls:
api_oauth2_authorize:
pattern: ^/api/oauth2/authorize$
http_basic: ~
provider: default
Similar as authorization endpoint, we need to protect this endpoint with our custom firewall oauth2_token:
# app/config/security.yml
security:
firewalls:
api_oauth2_token:
pattern: ^/api/oauth2/token$
oauth2_token: ~
We should protect this endpoint with our custom firewall oauth2_resource:
# app/config/security.yml
security:
firewalls:
api_oauth2_debug:
pattern: ^/api/oauth2/debug$
oauth2_resource: ~
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/config/security.yml
security:
firewalls:
api_resource:
pattern: ^/api/resource
oauth2_resource: ~
Longhand version (assume resource server bundled with authorization server, query local model manager, protect with scope demoscope1):
# app/config/security.yml
security:
firewalls:
api_resource:
pattern: ^/api/resource
oauth2_resource:
resource_type: model
scope: [ demoscope1 ]
If authorization server is hosting somewhere else, you can protect your local resource endpoint by query remote authorization server debug endpoint:
# app/config/security.yml
security:
firewalls:
api_resource:
pattern: ^/api/resource
oauth2_resource:
resource_type: debug_endpoint
scope: [ demoscope1 ]
options:
debug_endpoint: http://example.com/api/oauth2/debug
cache: true
The demo is based on Symfony and AuthBucketOAuth2Bundle. 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-symfony-bundle directory:
$ composer create-project authbucket/oauth2-symfony-bundle authbucket/oauth2-symfony-bundle "~5.0"
Then use the PHP built-in web server to run the demo application:
$ cd authbucket/oauth2-symfony-bundle
$ ./bin/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.
OAuth2Bundle's documentation is built with Sami and publicly hosted on GitHub Pages.
To built the documents locally, execute the following command:
$ sami.php update .sami.php
Open build/sami/index.html with your browser for the documents.
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:
$ phpunit -c phpunit.xml.dist
Open build/logs/html with your browser for the coverage report.