A spec compliant, secure by default PHP OAuth 2.0 Server
Go to file
2013-01-02 20:32:38 +00:00
build Ignore code coverage in ../tests folder 2013-01-02 19:12:53 +00:00
sql Added the user_credentials and refresh_token grants. Fixed expires_in so it is inline with the spec, but added expires for the old usage of expires_in. Made redirect_uri in oauth_sessions ALLOW NULL since user_credential grants don't have a redirect 2012-12-19 16:12:48 -05:00
src/Oauth2 Added support for refresh tokens, user credentials and client credentials grant. 100% unit test code coverage for authentication. Fixes #2 2013-01-02 19:14:22 +00:00
tests Another attempt to fix paths for travis 2013-01-02 20:32:38 +00:00
.gitattributes Added a .gitattributes file 2012-09-19 19:48:32 +01:00
.gitignore Removed old test bash file 2012-10-05 15:27:34 +01:00
.travis.yml Added .travis.yml 2012-12-30 21:31:19 +00:00
build.xml Don't remove composer.json and vendor dir 2012-08-06 16:13:27 +01:00
composer.json Version bump 2013-01-02 19:16:51 +00:00
license.txt Clarified license type 2012-07-19 15:32:38 +01:00
README.md Updated README 2013-01-02 19:16:16 +00:00

PHP OAuth Framework

The goal of this project is to develop a standards compliant OAuth 2 authentication server, resource server and client library with support for a major OAuth 2 providers.

Package Installation

The framework is provided as a Composer package which can be installed by adding the package to your composer.json file:

{
	"require": {
		"lncd\Oauth2": "*"
	}
}

Package Integration

Check out the wiki

Current Features

Authentication Server

The authentication server is a flexible class that supports the following grants:

  • authentication code
  • refresh token
  • client credentials
  • password (user credentials)

Resource Server

The resource server allows you to secure your API endpoints by checking for a valid OAuth access token in the request and ensuring the token has the correct permission to access resources.

Future Goals

Authentication Server

Client support


This code will be developed as part of the Linkey project which has been funded by JISC under the Access and Identity Management programme.