Page History

...

New and noteworthy

Support for MySQL 8

Thanks to dependency upgrade to Apache OpenJPA 3.1.0, this release can now be deployed with internal storage on MySQL 8.

Support for MySQL JSON Data Type

Similarly to PostgreSQL's JSONB support introduced with 2.1.3, this release brings support for MySQL's JSON data type

Issues

Bug

• [SYNCOPE-1428] - APIs to read by key return 404 instead of 401 for not authenticated calls
• [SYNCOPE-1429] - Wildcard case-insesitive queries do not work with Elasticsearch
• [SYNCOPE-1430] - ItemTransformer for Date schemas throws NPE
• [SYNCOPE-1431] - Connector and Resource history compare does not work
• [SYNCOPE-1432] - After creating new connector / resource, Topology does not show it
• [SYNCOPE-1437] - Error while searching for users / groups / any objects with Elasticsearch when no data are present
• [SYNCOPE-1438] - "changePwdDate" field is not initialized when create a new user with the specified password
• [SYNCOPE-1439] - User membership attributes not updated
• [SYNCOPE-1440] - Pagination of Users/Groups doesn't work as expected with Elasticsearch
• [SYNCOPE-1442] - Inactive Job with cron expression set is executed anyway
• [SYNCOPE-1443] - Changing Display Rows number in Reconciliation Resource Panel doesn't work
• [SYNCOPE-1446] - Persistence exception on PostgreSQL when AUDIT is enabled on propagation tasks
• [SYNCOPE-1447] - NPE while deleting a privilege from admin console
• [SYNCOPE-1448] - Bean loading/register section not threadsafe
• [SYNCOPE-1450] - Audit: sensitive information not masked by default during update
• [SYNCOPE-1452] - Notification about is not deleted after update
• [SYNCOPE-1453] - MappingItem with "mustChangePassword" field cannot be provisioned and updated during import
• [SYNCOPE-1454] - Avoid duplicated Propagation Tasks
• [SYNCOPE-1457] - NonAlphaNumeric policy pattern matches the "Not word" character class

...

New and noteworthy

Support for PostgreSQL JSONB Data Type

...

New and noteworthy

Request Management

Request management is a key-feature of Identity Governance and allows to define and manage, in a structured way, whatever process intended to update identity attributes, memberships and relationships.
Request examples are "assign mobile phone", "grant groups on AD" or "consent access to application".

...

New and noteworthy

Batch

Batch requests allow grouping multiple operations into a single HTTP request payload.
A batch request is represented as a Multipart MIME v1.0 message, a standard format allowing the representation of multiple parts, each of which may have a different content type (currently JSON, YAML or XML), within a single request.

...

New and noteworthy

Apache Groovy-based customizations

...