keystone

History

Ziad Sawalha 88d6c0dc09 Updated auth_token middleware caching to support memcache - Added support for memcache client (swift cache is not 100% compatible with it;it uses a timeout instead of time parameter) - Added the 'memcache_hosts' entry in the middleware ini file to support that. - Moved the caching logic to the _verify_claims call (so callers don't have to manage cache) - Added caching for bad/invalid tokens so they don't generate calls to Keystone - Added documentation for middleware configuration - Added documentation on caching configuration for middleware Change-Id: I9fc30186a91559ec8d50d90e887f5ee87669d38b		2011-12-03 10:44:32 -06:00
..
echo	Updated auth_token middleware caching to support memcache	2011-12-03 10:44:32 -06:00
paste	Updated auth_token middleware caching to support memcache	2011-12-03 10:44:32 -06:00
ssl	X.509 client authentication with Keystone. Implements blueprint 2-way-ssl	2011-11-04 16:47:33 -07:00
README.md	Merging keystone.auth_protocols package into keystone.middleware	2011-07-18 10:39:33 -05:00
__init__.py	Added py init files to directories already being referenced as modules	2011-06-15 14:27:19 -05:00

README.md

RUNNING THE TEST SERVICE (Echo.py):

Standalone stack (with Auth_Token)
$ cd echo/bin
$ ./echod

Distributed stack (with RemoteAuth local and Auth_Token remote)
$ cd echo/bin
$ ./echod --remote

in separate session
$ cd keystone/middleware
$ python auth_token.py

DEMO CLIENT:

A sample client that gets a token from Keystone and then uses it to call Echo (and a few other example calls):

$ cd echo/echo
$ python echo_client.py
Note: this requires test data. See section TESTING for initializing data