Sha256: bd14f5972bb713775786b1589e87e511fcfbb482a7209f13bdf78252536df695

Contents?: true

Size: 1.56 KB

Versions: 1

Compression:

Stored size: 1.56 KB

Contents

EasyRackOpenID. Simplifies OpenID login for Rack apps.

Get Rack::OpenID of http://github.com/josh/rack-openid
gem install rack-openid
gem install easy-rack-open-id

You:
require 'rack/openid'
use Rack::Session::Cookie
use Rack::OpenID
use EasyRackOpenID, :allowed_identifiers => ['http://example.com/']
run lambda {|env| [ 200, { 'Content-Type' => 'text/plain' }, [ 'Authenticated!' ] ] }

There's an example in config.ru


Basically, slap EasyRackOpenID in front of the App you want to protect. Rack::OpenID needs to be above it.
Rack:OpenID with noo arguments uses an in memory OpenID store. This is ok for trying out with rackup, but won't work in a variety of scenarios including using shotgun. You can pass it a different store like so:
use Rack::OpenID, OpenID::Store::Memcache.new

With no arguments, EasyRackOpenID will only allow users with a verified OpenID to proceed. It won't care what that identity is.

:allowed_identifiers - when used, only identities in the provided array will be allowed access.

:identity_match - when used, only identities matching this regex pattern will be allowed.

Right now allowed_identifiers and identity_match cannot both be used at once.

:default_return_to (optional) is a path just in case the automatic return_to mysteriously vanishes. Unlikely.

:login_path (optional) is where to send a user if login fails. Perhaps a login form?

:logout_path (optional, defaults to /logout) path that, when visited will clear the login session

:after_logout_path (optional) After a user logs out, send them here. (don't want the user sitting on the logout path)

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
easy-rack-open-id-0.0.2 README