This is not aa problem to define more methods.

   Replace it with an generic action directly pushed to erp5 (erp5_forge)

See merge request !606

   This prevent raise in case some non-ascii char is passed into the string.

  We only expand by the end of the period, so we dont generate an invoice 15 days in advance anymore

- make url script return no url if there are not connection parameters
- update tests accordingly

   ...to failures on password generation

See merge request !604

See merge request !603

   The password has to work accordinally the policy, if fail retry a few times.

   There is no more patch

  backport from ERP5

   In past, we used to rely on ERP5 Login (passwordless) for authentication via Certificates, but we switched to use excusively a dedicated portal type (Certificate Login).

   The ERP5 Login now follows the default implementation, so no need custom scripts.

   This helps to figure out what it is really testing.

  Some scripts were removed and on other cases started to be tested.

   After 6 years, it is expected that all instances are migrated. The migration is outdated, since it we use Certificate Login rather them ERP5 Login on Compute Nodes and Software Instances.

    There is no need to pre-create it, since it would be required you go throw External service (Facebook or Google) to create the default connectors.

See merge request !601

See merge request !600

See merge request !599

See merge request !596