summaryrefslogtreecommitdiff
path: root/README.md
blob: 3d872932dccb3c8cd719c14f36d758db4bf353d7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
oauth2-server-php
=================

[![Build Status](https://secure.travis-ci.org/bshaffer/oauth2-server-php.png)](http://travis-ci.org/bshaffer/oauth2-server-php)

A library for implementing an OAuth2 Server in php

[View the Full Working Demo!](http://brentertainment.com/oauth2) ([code](https://github.com/bshaffer/oauth2-server-demo))

Autoloading
-----------

This library follows the zend [PSR-0](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md) standards.  A number of
autoloaders exist which can autoload this library for that reason, but if you are not using one, you can register the `OAuth2_Autoloader`:

    require_once('/path/to/oauth2-server-php/src/OAuth2/Autoloader.php');
    OAuth2_Autoloader::register();

If you use a package library like [Composer](http://getcomposer.php), add the following to `composer.json`

    {
        "require": {
            "bshaffer/oauth2-server-php": "dev-master",
            ...
        },
        ...
    }

And then run `composer.phar install`

Get Started
-----------

Before getting started, take a look at the [Oauth2 Demo Application](http://brentertainment.com/oauth2) and the [source code](https://github.com/bshaffer/oauth2-server-demo) for a concrete example of this library in action.

The quickest way to get started is to use the following code, plugging in your database information
to the constructor of `OAuth2_Storage_Pdo`:

    $storage = new OAuth2_Storage_Pdo(array('dsn' => $dsn, 'username' => $username, 'password' => $password));
    $server = new OAuth2_Server($storage);
    $server->addGrantType(new OAuth2_GrantType_UserCredentials($storage)); // or some other grant type.  This is the simplest
    $server->handleGrantRequest(OAuth2_Request::createFromGlobals())->send();

Let's break this down line by line. The first line is how the OAuth2 data is stored.
There are several built in storage types, for your convenience.  To use PDO Storage,
instantiate the `OAuth2_Storage_Pdo` class and provide the database connection arguments:

    $storage = new OAuth2_Storage_Pdo(array('dsn' => $dsn, 'username' => $username, 'password' => $password));
    $server = new OAuth2_Server($storage);

The next step is to add a grant type.  This example uses the "User Credentials" grant type, which grants a token based on
explicit user credentials passed to the request. Read more on [supported grant types](https://github.com/bshaffer/oauth2-server-php#the-response-object)
below, or in the [OAuth2 spec](http://tools.ietf.org/html/draft-ietf-oauth-v2-20). Each grant type also requires storage,
so pass the existing storage to the constructor:

    $server->addGrantType(new OAuth2_GrantType_UserCredentials($storage));

Call the `grantAccessToken` method to validate the request for the user credentials grant type.  This will return the token
if successful.  Access the server's response object to send the successful response back, or the error response if applicable:

    $server->handleGrantRequest(OAuth2_Request::createFromGlobals())->send();

This creates the `OAuth2_Request` object from PHP global variables (most common, you can override this if need be) and sends it to the server
for assessment.  The response by default is in json format, and includes the access token if successful, and error codes if not.

Server Methods
--------------

> ...an end-user (resource owner) can grant a printing
> service (client) access to her protected photos stored at a photo
> sharing service (resource server), without sharing her username and
> password with the printing service.  Instead, she authenticates
> directly with a server trusted by the photo sharing service
> (authorization server), which issues the printing service delegation-
> specific credentials (access token).
>
>   ~ OAuth2 ([draft #31](http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-1))

Most OAuth2 APIs will have endpoints for `Authorize Requests`, `Grant Requests`, and `Access Requests`:

 * **Authorize Requests** - An endpoint requiring the user to authenticate, which redirects back to the client with an `authorization code`
 * **Grant Requests** - An endpoint which the client uses to exchange the `authorization code` for an `access token`
 * **Access Requests** - Any API method requiring oauth2 authentication.  The server will validate the incomming request, and then allow
the application to serve back the protected resource

For these tyes of requests, this library provides the following methods:

**Authorize Requests**

`handleAuthorizeRequest`
  * Receives a request object for an authorize request, returns a response object with the appropriate response

`validateAuthorizeRequest`
  * Receives a request object, returns a Boolean for whether the incoming request is a valid Authorize Request.
Applications should call this before displaying a login or authorization form to the user

**Grant Requests**

`grantAccessToken`

  * Receives a request object for a grant request, returns a token if the request is valid.

`handleGrantRequest`

  * Receives a request object for a grant request, returns a response object for the appropriate response.

`getClientCredentials`

  * parses the client credentials from the request and determines if they are valid

**Access Requests**

`verifyAccessRequest`

  * Receives a request object for an access request, finds the token if it exists, and returns a Boolean for whether
the incomming request is valid

`getAccessTokenData`

  * Takes a token string as an argument and returns the token data if applicable, or null if the token is invalid

The Response Object
-------------------

The response object serves the purpose of making your server OAuth2 compliant.  It will set the appropriate status codes, headers,
and response body for a valid or invalid oauth request.  To use it as it's simplest level, just send the output and exit:

    // will set headers, status code, and json response appropriately for success or failure
    $server->grantAccessToken();
    $server->getResponse()->send();

The response object can also be used to customize output. Below, if the request is NOT valid, the error is sent to the browser:

    if (!$token = $server->grantAccessToken()) {
        $server->getResponse()->send();
        die();
    }
    echo sprintf('Your token is %s!!', $token);

This will populate the appropriate error headers, and return a json error response.  If you do not want to send a JSON response,
the response object can be used to display the information in any other format:

    if (!$token = $server->grantAccessToken()) {
        $response = $server->getResponse();
        $parameters = $response->getParameters();

        // format as XML
        header("HTTP/1.1 " . $response->getStatusCode());
        header("Content-Type: text/xml");
        echo "<error><name>".$parameters['error']."</name><message>".$parameters['error_description']."</message></error>";
    }

This is very useful when working in a framework or existing codebase, where this library will not have full control of the response.

Grant Types
-----------

There are many supported grant types in the OAuth2 specification, and this library allows for the addition of custom grant types as well.
Supported grant types are as follows:

  1. [Authorization Code](http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.1)

        An authorization code obtained by user authorization is exchanged for a token

  2. [Implicit](http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.2)

        As part of user authorization, a token is retured to the client instead of an authorization code

  3. [Resource Owner Password Credentials](http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.3)

        The username and password are submitted as part of the request, and a token is issued upon successful authentication

  4. [Client Credentials](http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.4)

        The client can use their credentials to retrieve an access token directly, which will allow access to resources under the client's control

  4. [JWT Authorization Grant](http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-04#section-4)

        The client can submit a JWT (JSON Web Token) in a request to the token endpoint. An access token (without a refresh token) is then returned directly.

Create a custom grant type by implementing the `OAuth2_GrantTypeInterface` and adding it to the OAuth2 Server object.

Acknowledgements
----------------

This library is largely inspired and modified from [Quizlet's OAuth2 PHP library](https://github.com/quizlet/oauth2-php)

Contact
-------

The best way to get help and ask questions is to [file an issue](https://github.com/bshaffer/oauth2-server-php/issues/new).  This will
help answer questions for others as well.

If for whatever reason filing an issue does not make sense, contact Brent Shaffer (bshafs <at> gmail <dot> com)