plone.keyring contains a Zope3 utility that facilitates handling of secrets in an application. Secrets are very important in modern applications, which is why a shared tool to manage them is useful.
plone.keyring contains two basic components:
- a keyring: a data structures which contains one or more secrets.
- a key manager: a utility which contains the available keyrings and provides some convenience methods to manage them
The keyring is the workhorse: it contains a set of secrets for a specific purpose. A ring has room for a fixed number of secrets which is set at creation time. The most recently added secret is considered to be the current secret and the one that should be used. Older secrets in the ring can be used to keep data generated with older secrets valid for a period of time.
The key manager is a container for the available keyrings. It always contains a default system keyring which is used when no other ring is explicitly requested.
You’ll need to register a KeyManager as a persistent utility. On Zope2 with GenericSetup, this can be done by loading the included profile.
1.1 - May 2, 2008
- Add an optional GenericSetup profile to register the KeyManager as utility. Required for plone.keyring on Plone 3.0. [mj]
1.0 - April 21, 2008
- No changes [wichert]
1.0b1 - March 7, 2008
- Tweak the tests to better test the API. [witsch]
1.0a1 - January 22, 2008
- Initial release [wichert]
Release history Release notifications
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size plone.keyring-1.1-py2.4.egg (13.5 kB)||File type Egg||Python version 2.4||Upload date||Hashes View hashes|
|Filename, size plone.keyring-1.1.tar.gz (9.7 kB)||File type Source||Python version None||Upload date||Hashes View hashes|