Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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: https://itsense.atlassian.net/wiki/spaces/IKB/pages/2036400151/Token+Assignment+Context#roles_with_context_min .

  • 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: https://itsense.atlassian.net/wiki/spaces/IKB/pages/1992982615/Token#Claims-in-access-token .

  • 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.

  • There are two new quality of registration paths which don’t offer the manual option

  • Fidentity verification method

    • The 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

  • The default log configuration was adapted to keep the log files for 100 days and a maximum of 10 MB per day

  • Breaking change: The design was refined. Among various changes, there is now a default background image. Please review your design after the update and adjust to your CI / CD. You can disable the background image by adding background-image: none;

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.

...