(cherry picked from commit 7af4728b7463a521fadca3dcedbd5e445d9ef12e)

(cherry picked from commit 3fa79d0e6f1a771caae0f898e87e015486180975)

use the interpreter's import lock instead of threading.RLock in ERP5Type.dynamic to avoid possible dead lock.
(cherry picked from commit a29456bc)

Sometimes on configuration product-config can be defined but promise-path and
site id isn't, like for example when some instance use DeadlockDebugger.

As it is possible to do category_simulation_state=..., it shall be possible to
do same relation based on validation_state.

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.