Versions Compared

Version Old Version 3 New Version Current
Changes made by

Silvan Grüter

Roger Fankhauser

Saved on

Key

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

...

  • A auto-registration feature was implemented. When enabled on the external provider configuration, this will automatically create a user for external identities without displaying the registration form.

  • The sub used in the tokens can now be defined on the application configuration. This allows you to use any of the provisioned unique attributes as the sub.

  • The Level of Authentication has been renamed to Quality of Authentication and a Quality of Registration configuration has been added. With both you are able to build a Level of Trust as described in many standards such as eCH-0170 oder ISO/IEC 29115.

  • In order to check or improve the Quality of Registration, various verification methods have been integrated.

  • Automatic key rotation has been implemented. For further information check the documentation.

CoreOne Database Services

  • Breaking Change: Please make sure that you are using a MariaDB Version higher or equal to 10.5.2 and lower than 10.10 before updating.

  • Breaking Change: The default charset will be changed from latin1 to utf8mb4. This will be executed automatically with the installer, but on bigger installations, it’s recommended to execute the queries beforehand.

...

CoreOne Self-Service Portal

  • Breaking Change: The structure of the templates in the ProgramData folder changed. Changes made in the templates folder needs to be migrated to the new structure following these steps:

    • Stop the APPPOOL for AUTH and SELF SERVICE

    • Backup the contents in the folder C:\ProgramData\itsense\Templates, then delete them

    • Start the apppools and open AUTH and PORTAL once (this will recreate the folders)

    • Add and replace the files from the backup again (files that were changed are bigger than 0 KB)

  • There is a new help button. When enabled and used, users have the option to enter a support request and add attachments. Both the message and the attachments will then be sent to a workflow, from which the data can be processed. From within the workflow, the data can be sent to a ticketing system or sent via e-mail to support center.

...