Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Preview

CoreOne Admin User Interface

Features

  • A back-channel logout has been implemented.

CoreOne Authentication Services

Features

  • There is a new scope to request a new minified version of the roles_with_context claim. You can find more on this topic here.

  • Claim types can now be limited in size to make sure that tokens don’t surpass a certain size. You can find more on this topic here.

  • A reference to the external identity provider is passed to the CoreIdentityCreated workflow, so that the source of the registration is available from within the workflow. More on the configuration here.

  • Logout propagation to external identity providers has been implemented.

  • Minor design changes have been applied to improve readability and usability.

  • The validation of the place of birth in the AHV verification method has been made optional. You can set ValidatePlaceOfBirth to false in the configuration to do so.

  • Fidentity verification method

    • Then users language is now passed to the identity verification service fidentity.

    • The evidence files are now being downloaded and can be stored locally using a workflow

    • When the user is being deleted, the evidence files can be deleted using a workflow

Bug fixes

  • Breaking change: The issued roles_with_context claim had a ClaimValueType of CoreOne:iTsense.CoreLogin2.Shared.Models.RoleClaim.RoleClaim instead of urn:coreone:authentication:role:with_context. Should you somewhere reference to the old, incorrect value, please adjust it.

  • The username claim could not be used in the id_token and access_token because of its special storage type (multiple usernames are supported). It’s now possible to map the username to any scope.

CoreOne Application Services

Features

  • There are new workflows available to define approval workflows for both roles and roles types. You can find more on this topic here.

CoreOne Database Services

Features

  • -

CoreOne Self Service Portal

Features

  • A back-channel logout has been implemented.

  • Breaking change: The permissions to read the QoR and QoA have been removed from the default CoreOne Suite Self-Service User security role and added to an own role called CoreOne Suite Read Own QoR / QaA. This security role will also give you permissions to the appropriate Self-Service widget.

CoreOne System Connectors

Features

  • -

CoreOne Trustee Management App

Features

  • There is a new application setting to switch between the the new minified roles_with_context claim.

CoreOne Workflow Services

  • There are new DMS workflow activities to search, create and delete documents

  • No labels