Preview |
The format of the role claim used to issues permissions can now be defined as either an array or as a separated list. This can be configured on the application level and appropriate UI masks have been added.
There is a new event that is thrown when a delegated permission is being suspended in the Self-Service Portal.
Breaking-Change: As we now distinguish between the deactivation of a delegated permission (the users deactivates the delegated permission) and the suspension (the user deactivates the representation relationship and thus the delegation will be suspended), the two existing events (Deactivated and Reactivated) were extended by a flag that tells you, whether or not the delegated permission was suspended or not: WasSuspended. You might wanna account for that new flag in any of the workflows that you have configured.
The error handling workflows executed during deprovisioning of identities and resources has been improved.
SAML assertion passing has been added. This allows you to simply pass SAML assertions from an external federation party to tokens.
The format of the role claim used to issues permissions can now be defined as either an array or as a separated list. This can be configured on the application level.
The sign_assertions settings of SAML service providers was mapped incorrectly to the setting encrypt_assertions. This meant, that even tough you enabled the sign_assertions settings, assertions were not signed unless the setting encrypt_assertions was enabled.
The validation rules for mobile numbers were unified across all screens.
The private policies and terms and conditions checkboxes on the registration masks missed proper translations if the user did not accept them.
When no reset method was available for a user, there was no appropriate log entry in the logs. An appropriate log entry has been added to simplify tracing.
Validation has been improved further on the registration mask. The submit form button was not always blocked before the async validation was finished.
The installer now can handle both aspnetcoremodulev1 and aspnetcoremodulev2. The later has become the default in Windows Server 2022.
The CoreOne Suite Shop resource had insufficient rights to order something if a user only had this role
There are new workflow activities to read attribute definitions.
If the condition HighestEmploymentDate was utilized in any of the workflows, employments that were marked as deleted still contributed to the calculation.
The activity GetDiVor used the wrong HTTP method to load the data resulting in an error.
The ValidFrom and ValidTo date times of the CreateCoreIdentityEmploymentWorkflowInput and the AfterUpdate event of a resource assignment where passed in local time to the workflows and the CoreOne Workflow Engine assumed it’s UTC. Both dates are now passed in UTC to the workflows.
When changing the ReadOnlyEmail property of a Core Identity, the CoreIdentityChanged workflow was not triggered. This workflow, along with the generic AfterUpdate workflow is now being triggered.