Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

One of the most noticeable advantages of Apache Syncope is in its extreme flexibility: since the early days, in fact, practically any aspect of the system can be tweaked and customized to adapt to the various needs that might be encountered during deployments.
In most cases, this boils to down to code some Java class, add it to own Syncope project, rebuild and redeploy to see it at work. Naturally, this can be possible only when there is a local Maven project: other artifacts as Docker images, Debian packages or Standalone Distribution are simply not applicable.

With SYNCOPE-956 In Syncope 2.1 Fusion it is possible to provide implementations in Apache Groovy, without losing any customization capability: this implies:

  1. faster development cycle: no need to rebuild and redeploy to apply the changes
  2. possibility to customize the behavior of Docker images, Debian packages and Standalone Distribution

Privilege Management

Enables Syncope with the ability to define, map and query the rights that users own on external applications.

Remediation

Errors during pull might arise for various reasons: values might not be provided for all mandatory attributes or fail the configured validation, delete User as consequence of an incremental change’s processing might be blocked because such User is configured as Group owner, and so on.

When Remediation is enabled for a certain Pull Task, execution errors are reported to administrators, which are given the chance to examine and possibly fix, or just discard.

Flowable 6

The Flowable User Workflow Adapter was available since Syncope 2.0, as an alternative to Activiti; Syncope 2.1 Fusion embeds the latest evolution of Flowable 6 as the reference workflow engine.

How to upgrade from 2.0

Upgrading from 2.0? There are some notes about this process

...