repoze-oauth-plugin 0.1.1

repoze-oauth-plugin is a repoze.who and repoze.what plugin implementing the server side of the OAuth 1.0 protocol. Currently it supports only 2-legged flow where the client is at the same time a resource owner. This happens when a client application has access to the resources on the server on behalf of itself and does not need a user (human) permission for the access.<br /><br />You can read more about OAuth at hueniverse (2-legged flow).<br /><br />Installation<br /><br />easy_install:<br /><br />$ < env >/bin/easy_install repoze-oauth-plugin<br /><br />pip:<br /><br />$ < env >/bin/pip install repoze-oauth-plugin<br /><br />OAuthPlugin Usage<br /><br />You can create the plugin with:<br /><br />>>> from repoze.who.plugins.oauth import OAuthPlugin<br />>>> oauth_plugin = OAuthPlugin(DBSession=Session,<br />... Manager=MyManager,<br />... realm='my-realm')<br /><br />where:<br /><br /> * Session is an SQLAlchemy Session bound to a valid engine. If you are configuring the plugin through the PasteDeploy configuration file this can be an entry point, e.g. myproject.model.meta:Session.<br /> * Manager (optional) is a class that is responsible for client management in the database. Default - repoze.who.plugins.oauth:DefaultManager. The Manager has to take the Session as an initialization parameter and provide a get_consumer_by_key(key) instance method. Can be provided as an entry point too.<br /> * realm (optional) - a realm identifying the protection space.<br /><br />The repoze.who plugin in repoze-oauth-plugin acts as an Identifier, Authenticator and Challenger. Therefore to get OAuth support you need to give it as identifier, authenticator and challenger to the repoze.who middleware, similar to this (here we create it using repoze.what provided helper):<br /><br />>>> oauth_plugin = OAuthPlugin(Session, realm='MyRealm')<br />>>> from repoze.what.middleware import setup_auth<br />>>> app = PluggableAuthenticationMiddleware(my_app,<br />... group_adapters=my_group_adapters,<br />... permission_adapters=my_permission_adapters,<br />... identifiers=[('oauth', plugin)],<br />... authenticators=[('oauth', plugin)],<br />... challengers=[('oauth', plugin)],<br />... **other_kwargs)<br /><br />However, usually you would use some higher level middleware maker. Let's take repoze.what-quickstart as an example:<br /><br />>>> oauth_plugin = OAuthPlugin(Session, realm='MyRealm')<br />>>> from repoze.what.plugins.quickstart import setup_sql_auth<br />>>> app = setup_sql_auth(app, User, Group, Permission, Session,<br />... identifiers=[('oauth', oauth_plugin)],<br />... authenticators=[('oauth', oauth_plugin)],<br />... challengers=[('oauth', oauth_plugin)])<br /><br />repoze-oauth-plugin uses oauth2 for OAuth specific functionality and plays well with restkit.<br /><br />Predicate Usage<br /><br />If you have set the OAuthPlugin with setup_sql_auth (or any other way that includes repoze.what support) you can use OAuth specific predicates provided by repoze-oauth-plugin.<br /><br />is_consumer([consumer_key=None]) is a predicate that checks whether the current user is a consumer acting on behalf of itself (2-legged flow):<br /><br />>>> from repoze.what.plugins.oauth import is_consumer<br />>>> p = is_consumer()<br />>>> p.check_authorization(environ)<br />Traceback (most recent call last):<br />...<br />repoze.what.predicates.NotAuthorizedError: The current user must be a consumer<br /><br />Ask for a consumer with a particular key:<br /><br />>>> p = is_consumer('my-app')<br /><br />not_oauth() is a predicate that denies access through OAuth. All other methods are allowed (even anonymous!):<br /><br />>>> from repoze.what.plugins.oauth import not_oauth<br />>>> p = not_oauth()<br />>>> p.check_authorization(environ_with_oauth)<br />Traceback (most recent call last):<br />...<br />repoze.what.predicates.NotAuthorizedError: Access through OAuth forbidden<br />>>> p.check_authorization({}) # Empty environ, no user - ok!<br /><br />Pylons setup<br /><br />The following is an example setup for a Pylons application. Let's assume it is called ExampleApp. We'll use repoze.what-quickstart and repoze.what-pylons:<br /><br />$ < env >/bin/pip install repoze.what-quickstart repoze.what-pylons<br /><br />First, in your exampleapp/config/middleware.py file define imports:<br /><br />from repoze.what.plugins.quickstart import setup_sql_auth<br />from repoze.who.plugins.oauth import OAuthPlugin<br /><br />from exampleapp.model import User, Group, Permission<br />from exampleapp.model.meta import Session<br /><br />then just below:<br /><br /># The Pylons WSGI app<br />app = PylonsApp(config=config)<br /><br />create the repoze-oauth-plugin and provide a realm and SQLAlchemy session:<br /><br />oauth_plugin = OAuthPlugin(realm='exampleapp', DBSession=Session)<br />app = setup_sql_auth(app, User, Group, Permission, Session,<br /> identifiers=[('oauth', oauth_plugin)],<br /> authenticators=[('oauth', oauth_plugin)],<br /> challengers=[('oauth', oauth_plugin)])<br /><br />According to the OAuth specification in case of 401 Unauthorized the server has to return a WWW-Authenticate: OAuth realm="..." header. Pylons StatusCodeRedirect middleware replaces the 401 response with its own custom 401 response discarding even the headers set by the downstream application. In order to avoid this StatusCodeRedirect can be configured to not intercept the 401 response. In exampleapp/config/middleware.py replace:<br /><br /># Display error documents for 401, 403, 404 status codes (and<br /># 500 when debug is disabled)<br />if asbool(config['debug']):<br /> app = StatusCodeRedirect(app)<br />else:<br /> app = StatusCodeRedirect(app, [400, 401, 403, 404, 500])<br /><br />with:<br /><br /># Display error documents for 400, 403, 404 status codes (and<br /># 500 when debug is disabled)<br />if asbool(config['debug']):<br /> app = StatusCodeRedirect(app, [400, 403, 404])<br />else:<br /> app = StatusCodeRedirect(app, [400, 403, 404, 500])<br /><br />With the above setup you will have the OAuth consumer information in the environment whenever successful authentication happens.<br /><br />In order to be sure that only valid consumers can access your controllers and actions you have to protect them with repoze.what-pylons predicates:<br /><br /># exampleapp/controllers/cars.py<br />...<br />from repoze.what.plugins.pylonshq import ActionProtector<br />from repoze.what.plugins.oauth import is_consumer, not_oauth<br /><br />class CarsController(BaseController):<br /><br /> @ActionProtector(is_consumer)<br /> def index(self):<br /> return 'Hello, Consumer'<br /><br /> @ActionProtector(not_oauth)<br /> def public(self):<br /> return 'Not for consumer'<br /><br /><br /># exampleapp/controllers/trucks.py<br />...<br />from repoze.what.plugins.pylonshq import ControllerProtector<br />from repoze.what.plugins.oauth import is_consumer<br /><br />class TrucksController(BaseController):<br /><br /> def index(self):<br /> return 'Hello, all consumers'<br /><br />TrucksController = ControllerProtector(is_consumer)(TrucksController)<br /><br />Now these actions can be accessed using restkit:<br /><br />>>> from restkit import OAuthFilter, request, oauth2<br />>>> consumer = oauth2.Consumer(key='the-consumer',<br />... secret='the-consumer-secret')<br />>>> auth = OAuthFilter(('*', consumer))<br />>>> resp = request('http://localhost:5000/cars/index', filters=[auth])<br />>>> print resp.body<br /><br />#md5=a15aafbec78f941c73c38528aef87c21

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Authenticators Oauth,  Challengers Oauth,  Consumer,  Group,  Identifiers Oauth,  Import,  Oauth,  Oauth Plugin,  Plugin,  Pylons,  Re,  Repoze,  Repozeoauthplugin,  Repozewhat,  Repozewhatpluginsoauth,  Repozewhatquickstart,  Repozewho,  Response,  Return,  Server,  Session
Users rating:	0/10