Note |
---|
Preview |
CoreOne Authentication Services
...
CoreOne Application Interface
Bug fixes
Potential breaking change: Resetting or setting the password of a user over the API was no longer possible for identities, where the identity type did not have the feature
Is Logon Provider Active
activated. This dependency was introduced in an earlier version and was not correct. This issue has been resolvednot possible if thelogon_provider_active
was set to false. While fixing this issue it was also disovered that the flag was calculated incorrectly. It now checks if thelogon_provider_active
is active for both the identity type and the target system. This could lead to users on existing systems to not be able to login anymore if the flag is not set on both systems! Please check this after updating.
CoreOne System Connectors
...
Clearing the
managerUuid
field over the OpenLDAP Connector was not possible. This issue has been fixed.Fixed an issue where the
IdentityFindObjectIdInTargetSystem
activity in the OpenLDAP connector was not workingFixed an issue where a
cn
wasn't provisioned after shortening its value in the Active Directory system connectorFixed searching for Microsoft 365 groups while creating a linked resource
CoreOne Workflow Services
...
Breaking Change: The activity
Find object id in target system
threw an error, when no object was found. With the new version of the activity, you have a separateNo Match
path in the designer.The introduction of the credential manager lead to empty secrets being stored in existing workflow definitions. The issue has been resolved, no further action is required.
Breaking Change The activityHttpRequest has to be checked if the property Authorization is set correctly, if not it has to be edited in the designer.
Not correct json:
Code Block { "$id": "xx", "name": "Authorization", "expressions": { "$id": "yy" } }
Correct json:
Code Block { "$id": "xx", "name": "Authorization", "expressions": { "$id": "yy", "Secret": "empty" } }