Release date: 2026-11-02
Features
|
Jira ticket number |
Jira ticket number |
|---|---|
|
CRED-16881 |
When configuring HTTP clients in Identity Manager Admin, you can now extract content from the response headers. See the info button on the Response Configuration tab. |
|
CRED-18926 |
You can now set a timeout for HTTP Client calls in Identity Manager Admin. |
|
CRED-18968 |
Library update for the ADCS connector. SHA1 support is removed. See Integrate Identity Manager with Microsoft ADCS for details. |
|
CRED-21563 |
In case an error is returned when you are using HTTP clients, the response is now available in the process map. |
|
CRED-23452 |
You can now import endpoints from an Open API specification when configuring HTTP client collections in Identity Manager Admin. |
|
CRED-23637 |
Security library upgrade. |
|
CRED-23776 |
Security library upgrade. |
|
CRED-23788 |
Security update. |
|
CRED-23794 |
Security library upgrades for Identity Manager and Smart ID Self-Service. |
|
CRED-23865 |
Security library upgrades for Identity Manager and Smart ID Self-Service. |
|
CRED-23989 |
Library upgrade for high vulnerabilities. |
|
CRED-23999 |
Security library upgrades for Identity Manager and Smart ID Self-Service. See Upgrade Smart ID Identity Manager from 5.3.2 to 5.3.3 for more information. |
|
CRED-24088 |
Library upgrade for critical vulnerabilities. |
|
CRED-24089 |
Library upgrade for high vulnerabilities. |
|
CRED-24090 |
Library upgrade for high vulnerabilities. |
|
CRED-24111 |
Critical security library upgrade. |
|
CRED-24267 |
Security library upgrade. |
Corrected bugs
|
Jira ticket number |
Jira ticket number |
|---|---|
|
CRED-21900 |
When using the request type Multipart in HTTP clients, the names of the entries sent were not double quoted. This has been fixed. |
|
CRED-23125 |
In Identity Manager Admin, when importing a bpmn file for a process that already exists, there was an issue where the logo and single user process flag were reset to default values. This has been fixed. |
|
CRED-23557 |
There were some problems in update_db especially (but not only) with postgres DBs. This has been fixed. |
|
CRED-23629 |
There was a problem with permissions in asynchronous processes. This has been fixed. |
|
CRED-23732 |
When configuring HTTP clients in Identity Manager Admin, it is now possible to extract xml-attributes from the response using xpath expressions. |
|
CRED-23903 |
Access to open tasks in Smart ID Self-Service is now restricted by a permission instead of a UI configuration in Smart ID Self-Service. See See Upgrade Smart ID Identity Manager from 5.3.2 to 5.3.3for more information. |
|
CRED-24062 |
There was a problem with referencing user details for a non-core object authentication profile. This has been fixed. |
|
CRED-24076 |
Use of transport-key for card encodings via Smart ID Desktop App is now mandatory, since all Smart ID Desktop App versions supported by Identity Manager 5.1.0 or later can use it. See Upgrade Smart ID Identity Manager from 5.3.2 to 5.3.3 for more information. |
|
CRED-24182 |
There was an issue in Smart ID Self-Service where a user would stay on the login page even though client certificate authentication was successful. This has been fixed. |
|
CRED-24183 |
When searching for a certificate in Certificate Manager by serial number, the serial number supplied was not correctly converted and let to problems in some cases. This has been fixed. |
|
CRED-24277 |
There was a problem in HTTP client when using variables in application/x-www-form-url encoded requests. This has been fixed. |
|
CRED-24371 |
When using SAML login, there was no logging about login attempts. This has been fixed. |