real security configuration should still remain in sub module (modify 4610f372 a bit).

ref. http://comments.gmane.org/gmane.comp.web.zope.cvs/22117

ref. http://comments.gmane.org/gmane.comp.web.zope.cvs/22117

fix class tool's dtml files so that it works on Zope-2.12.23 too. also add some assertions to check if it works.

Revert "define __getitem__ instead of _getOb in class tool so that it works on Zope-2.12.23 too." that broke some tests.

This reverts commit 8670f40a.

Data can be really complex string, which can be bad for tag.

Use volatile cache to store tokens and one key per site.

Token server can be totally different then resource server.

Return token on addition.
Use proxied scripts to access whole system in order to allow unprivileged user
to manage own tokens.
Update roles immediately in order to give unprivileged user access to
validated token.

By requiring token_validation_method extraction plugin is only responsible
for low level implementation.

BearerTokenModule_addNewToken allows to add token for Person passed as
destination_reference. In case if Person has no key assigned new one is
generated.

BearerToken_isValid allows to validate token against (possibly) related person
object.

Base_getHMAC is low level interface to hmac module.

In order to made tokens unique use User-Agent and REMOTE_ADDR in token
generation body. Thanks to this token will be narrowed to one broswer. In order
to avoid reuse token on different servers add Host.

Key to generate HMAC are stored on Person object using bearer_token_key property.

Bearer is token used in OAuth 2. This plugin extracts this token from
Authorisation header and uses defined portal type query in order to check
if token is valid and for which user.

Allow to edit Role Information using proper category (forgotten commit from 5272e987).

Remove not used proeprty.