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

Having two listbox with the same ID displayed on the same page prevent expected usage of them, as the same parameter names are sent twice.

Note: Generic code shall have no constraints at all.

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.

PayZen interface expectes all dates in UTC, but suds library is not configurable.
So force UTC usage while importing and using suds, so no date mangling will happen.

Whitespaces shall be encoded with %digit

Allow recurse calls with uid, just disallow in public method.

uid is used internally during recursive calls and using uid can lead to
traverse all lines of catalog.

Conflicts:
	product/ERP5/bootstrap/erp5_core/bt/revision
	product/Zelenium/selenium/core/scripts/htmlutils.js
	product/Zelenium/selenium/core/scripts/selenium-api.js
	product/Zelenium/selenium/core/scripts/selenium-browserbot.js

This reverts commit ec8aa158 partially in order
to reenable:
- delivery_causality_interaction_workflow
- delivery_movement_causality_interaction_workflow
- simulation_movement_causality_interaction_workflow

These interaction workflows do not generate activities directly, and do work
that can't be postponed.

By contrast, 'calculate' transition of delivery_causality_workflow is modified
so that no 'updateCausalityState' activity is created by default.