Validation right for scopes on oauth2. #72
Fix test cases for validation #72
Merge branch 'master' of github.com:lepture/flask-oauthlib
Fix for oauthlib 0.6.1, add client_authentication_required

https://github.com/idan/oauthlib/commit/dff8e6d170f8028c9169bde1d208c1cccbea5aae
Handle empty response of json. close #69
Prepare for the next release of 0.4.3
Add the ability to pass additional URL parameters to the authorize() call
Release 0.4.3
Confidential client can obtain Authorization Code grant flow.
https://github.com/lepture/flask-oauthlib/issues/82
Fix issue where a different method was used for signing OauthV1 requests than the method used to request them.
Fix client_credentials logic in validate_grant_type

request.user was never set since grant_type was valid in the
implemented allowed_grant_types method.

This also updates the Client-model in oauth2-test to include
allowed_grant_types to be sure that this fixes the bug.
Fix code style with less ident
Remove `oauth` param in `require_oauth` decorator.
Clean OAuth2 Provider.
Remove `oauth` param in `require_oauth` decorator.
Clean OAuth1 Provider
Concept for session authentication and oauth authentication.
https://github.com/lepture/flask-oauthlib/issues/87
Request token params for OAuth1.
https://github.com/lepture/flask-oauthlib/issues/91
raise Exception when there is no token.

https://github.com/lepture/flask-oauthlib/issues/71
Example changes for facebook.
Related issue: https://github.com/lepture/flask-oauthlib/issues/90
Verify client secret. This is a secure bug.

https://github.com/lepture/flask-oauthlib/issues/92
Support client authentication for authorization-code grant type

When using a confidential client it should be possible to obtain
a token through authorization code grant type with a valid code.

This makes `OAuth2RequestValidator.validate_code()` and
`OAuth2RequestValidator.confirm_redirect_uri)` support retrieving
client from either request.client or request.client_id.