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

- Use _[ds]etOb instead of _[ds]etObject and unindex old object only if
  required. This improves performance and workarounds a bug documented in
  test_02_unindexObjectDependency.
- Automatically fix 'portal_type' attribute if required.

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

- Avoid overhead of getPropertyList & getXxx accessors
- Acquisition is useless for 'specialise' category on Simulation Movements.
  Maybe the same optimization can be done for all categories ?

Just a small performance improvement, the behavior still the same.
Because when the client send a big file, it should not take too long to check the sha512 sum.

Shacache instance is now able to provide big file without getting killed
by the OS, due a memory leak.

Desactivating the previous object is an approach to send the data without
overloading the RAM Memory.

provided.
Fallback means that no authentication policy will be applied if former
is true.

password recovery process in case of expired passwords.

to respective iLoginAccountProvider implementation class.

password expire occurs.

delete a needless object instead of alling delete transition, because such transition does not exist in certain states.

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

or not and use it respectively in isauthenticationPolicyenabled API.
Fix interaction workflow to catch all kind of possible setters.

Allow low level password validity checks (if
isAuthenticationPolicyEnabled only).
Adjust tests to handle better password history.

This parameter comes from catalog_join branch,where it is used to pass
a marker value (equivalent to an " AND " from SQL point of view).

catalog_join branch's code relies on this join condition ordering.
This simplifies template a bit (we don't generate slot names dynamically)
but makes variable meaning more obscure.

Sites migrated from Zope 2.8 don't have a configured component manager (a.k.a.
SiteManager) and because of that, and its consequent lack of registration of
the Localizer Message Catalogs as ITranslationDomain utilities, they don't
perform translation correctly.

Here we add a no-additional-cost migration by overriding the
ObjectManager.getSiteManager() method, and automatically configuring the
component manager, including translation domains.