Messages) are to be stored inside CRM event_module.

Recovery | Update

Create (and open Assingmnet) before validating Person object.

change authentication cookie as well at client side in same transaction.
This way a logged in user is able to change current password without
being kicked out of the system within.

is set or will be set later (through a Credential Recovery).

Return result of redirect call as it's used
in testERP5Credential.

password generation (either system sets it(default) or system generates
a Credential Recovery process which allows user set it through one time
active link)

security question (default is ask).

not.

requesting a new account or resetting a password to respective
login_form.

Support classical style and web site style.

Provide new preference, which if set can be used to find portal global
contract document.

954e399c introduced typos.

Provide sensible defaults.

When form is rendered while being not logged in, what is default way of using
this form, ERP5Site_getAuthenticatedMemberPersonValue returns None, so add
condition which does not log failures.

As users can double click (or register in same time with same reference)
during time of indexation, it is required to lock on activity system.

Note that as reference is global in the system, same tag, as in
Document.Person._setReference is used.

There is no need that credential update shall do anything with person
assingments. Especially there is no need to set same categories on all
assignments.