Preview

This release will soon be merged into the 9.1 release and therefore this page will be deleted

CoreOne Admin User Interface

Fixed an issue on the resource provisioning configuration where it wasn’t possible to remove an existing workflow anymore

CoreOne Authentication Services

Breaking Change: In order to access the Permission API (/api/permission), users now must have the CoreOne Authentication Service API Read Permissions for any Application resource assigned. As the name suggests, this endpoint allows to read all the permission of any applications!
A new Permission API that will only return the permission based on the token (and the associated client / application) has been added (/api/permission/myapplication). More information can be found here.

Fixed an issue in the registration process where it could lead to an error when changing the language
The anonymization of users did not anonymize the read only email address on the Core Identity and worked not correctly in some cases
SMS sent while in the registration process did not always include the screen reader version

The column attribute_edit_mode_id has been dropped from the table servicedmcore_core_identity_type_attribute_mapping as they are no longer needed

When selecting a date on the Auto-Ident initialization screen, users might have been redirected to the wrong destination. This happend when users selected a date from the previous month. So for example, when the selector was in June but the user selected the last day of May
A feedback message is now being shown when a successful support request was started

Fixed an issue with the WIKO system connector attribute bindings that were wrong
Deleting of CoreOne Suite users was throwing an error because of their authentication devices, this got fixed
The APIv2 method find-object-id-in-target-system wasn’t working when the searched attribute was the common name (CN) ← NOT YET FIXED