GitLab

SchedulerRMProxy : terminate active objects when login is not successful

This was creating a thread leaks with recurring unsuccessful login.

* Change the user group of the buckets created in ordered_bucket_list

Add new method permissions

* 'add-requests-to-check-permissions'

* add-annotations-to-serialize

* refactor-after-code-review

* refactor-after-code-review

* refactor-method-name
Co-authored-by: Oana Schiopu <oana-schiopu@activeeon.com>

* Specify the bucket owner before the initialization of the catalog

* encode workflow name

Fix global variables and generic info issue

variables or generic info present in the workflow was added to global variables. The parser was manipulating the global maps during workflow parsing
 - fixed by returning global data by copy instead of reference
 - added unit tests

Add sessionid to scripts

Improve error handling when scripts are not accessible (url fetching is done on the node side and not the server)

TestOperationsWhenUnlinked

Add sessionid to scripts

 - PerUserConnectionRMProxiesManager creates a rest session for each user
 - This works only if the rest server is launched in the same JVM as the scheduler server
 - sessionids are propagated to selection (via RMProxy and Criteria), task (TimedDoAction), pre, post, forkenv, flow (TaskLaunchedInitializer) and clean scripts (RMProxy)
 - The script must be "cloned" before execution, the original Script object, reference by InternalTask must not be modified. Otherwise, it would break the late binding reference mechanism, allowing to edit the script definition on task restarts.

Update miredot licence

Global variables: use LinkedHashMap

Global variables: add parser option to skip global variables handling

Add new Global variables mechanism

 - relax-ng schema for global variables configuration
 - configuration parser (refreshed periodically)
 - global variables and/or generic info can be applied to submitted workflows according to xpath filters
 - added unit tests
 - Handled the special case of schedulerapi (SchedulerNodeClient). When a task submits a new workflow, we expect this new workflow to preserve by default the global variables values (if overridden).

RM Rest client: rebuild server-side exceptions

fix-null-value

third-party-cred-trim-key

Do not rewrite uris which contain automation-dashboard

Fix private key issue

Disable security headers for rm portal popup window