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 Authentication Services

Features

  • The SamlTimeComparisonTolerance setting was only available for the Identity Provider. This setting was used to determinate the SamlTimeComparisonTolerance when the CoreOne Authentication Services act as IdP. When federating to external identity providers, such a setting was not available. An appropriate setting has been added to the external logon SAML configuration. More details can be found here.

  • The Fidentity verification method now supports the introduced vizValue of the October 2024 releases. More details can be found here.

  • Reading back the vizValue can lead to unwanted changes to the name, for example if the vizValue is sent back with all characters being uppercase. This got addressed by retaining the initial value of the name if all characters are matching. For example if Mr. McManus performs a registration but fidentity resolves the name to Mcmanus as he has a German passport with all uppercase names, we want to retain McManus, as entered by the user.

  • Support for double-barrelled name has been added to the AHV check.

Bugfixes

  • Some possible CSRF vulnerability attacks got fixed.

CoreOne Application Interface

Features

  • Improved the handling of firing events.

  • Improved the internal task management handling for the work item locks.

  • The overall task handling and the task performance has been improved.

Bugfixes

  • Handling of fast track tasks got adjusted to prevent a possible backend crash.

CoreOne Admin User Interface 2.0

Bugfixes

  • Fixed reading the locale of a country code (for example the “ch” part of “de-ch”) to correctly apply the language translations.

CoreOne Self-Service Portal

Bugfixes

  • The performance of the Self-Service Portal for users with a lot of companies associated (100+ companies) has been improved.

Database

  • Breaking change: Execute these statements after the update:

 SQL statement
SELECT COUNT(*) INTO @index_exists
FROM information_schema.statistics
WHERE table_name = 'taskscheduler_task_workitem_lock'
  AND index_name = 'IDX_22ACA89994B19A8683918539C5E9C67AE6C72D6E_GENERATED';

-- Conditionally drop the index
SET @drop_stmt = IF(@index_exists > 0, 'ALTER TABLE taskscheduler_task_workitem_lock DROP INDEX IDX_22ACA89994B19A8683918539C5E9C67AE6C72D6E_GENERATED', 'SELECT ''Index does not exist.''');
PREPARE stmt FROM @drop_stmt;
EXECUTE stmt;
DEALLOCATE PREPARE stmt;

INSERT IGNORE INTO api_action__api_security_resource	(api_action_id, api_security_resource_id) VALUES
	 (0x31F72A7AF0B0FDCF5A0FEAFB2D147472E5539FAC,2),
	 (0xC41B3D04D9A121AFE0BA91D72B2CC09F1F3A45ED,2),
	 (0xDFE5E829287B840C672FAAD1E4060606D66C8478,2);

  • No labels