getId is invoked before the updateLocalRolesOnSecurityGroups is invoked, so Shadow user has no permission on the context.

This workflow only makes it everything slow for no benefit.

Added a new movement group
Delivery Builder was reconfigured to perform accordinally

See merge request nexedi/slapos.core!229

See merge request nexedi/slapos.core!227

including the edge case where software permissions have been changed

This is usefull for display warning related to mantainence or changes of policies.

slapos_erp5: Accelarate Login by ignoring security_uids when scripts Login_is** scripts are called as manager

This avoid extra checks when login is related to Computer or Software Instances.

slapos_jio: Test password before reset it and give feedback when password don't comply with the policy

Just update to follow up fixes already done on the english version

  Test if the user adds a password that isn't complaint with the policy
  Try to logout and login with the new password
  Add test for the use removes the login he is using
  Add test for the user changes password he is using
  Include translated version of the tests to manage password

Mostly handle the response a bit better, and log out user if he changes the current login. This prevents his account get blocked.

This gadget aims to centralise entire "helper" test on various contexts, in this way translate becomes easy and update information is quite simple.

In order to use the gadget, you should include a template on rjs_gadget_slapos_annotated_helper_html:

<script id="add-new-example-header-text" type="text/x-handlebars-template">
Some text or <details> <summary>Some test<summary> <p>Content...</p></details>
</script>

and include the gadget on the target HTML:

<div data-gadget-url="gadget_slapos_annotated_helper.html"
data-gadget-scope="annotated_helper"
data-template-id="add-new-example-header-text"
data-gadget-sandbox="public">
</div>

This is also supposed to be compatible with GadgetField or usable from getDeclaredGadget(...)

  This prevents display error page when something is invalid using JIO API.

This is just annoying to have failures from tic because portal_activities is enabled on a development instance.

This tests the fix for "slapos_jio: fix ERP5Site_activeLogin"

Those files might be customize on project related business templates, so we don't want to overwrite those files.