Intelligent Adaptive Authentication September Release – 26.R3

Prev Next

Important notices

Stricter user data validation

Breaking change planned for Q4 2026: stricter user data validation

In the next release of Intelligent Adaptive Authentication, planned for Q4 2026, for calls to create and/or update users, a new validation will be introduced for the USERFLD_EMAIL and USERFLD_MOBILE fields. Currently, the Authentication component is returning status code 200 HTTP status OK (RET_SUCCESS/STAT_SUCCESS) when the user’s email address or phone number is invalid. Once the new validation, implemented in the Authentication component, is integrated in Intelligent Adaptive Authentication, these user data will be strictly validated, and the following applies whenever you create or update user accounts:

  • Email addresses:

    Email addresses will only be accepted if they are well formed and do not contain special characters. I.e., the address must only consist of digits, characters from the Latin (extended with accents), Cyrillic, and Arabic alphabets, and typical email punctuation.

  • Phone numbers:

    Only numbers that comply with ITU-T E.164 will be accepted.

If the format of the user’s email address and/or phone number is invalid, the Authentication component will be returning the 400 HTTP bad request (RET_FAILURE/STAT_INVDATA) error messages.

Make sure that your integration of Intelligent Adaptive Authentication is updated in time to avoid receiving errors for the stricter data validation.

This affects the following endpoints:

Existing user information fields are kept as is and are only revalidated when you attempt to update them

Deprecated or removed components and services

Deprecated endpoint: generate virtual signature

As of version 26.R3, the endpoint for the Virtual Signature feature, POST /users/{userID@domain}/generate-virtual-signature, is marked as deprecated. It will be completely removed from the OneSpan Trusted Identity platform API at the end of Q2 2027. Until then, the endpoint is still available but we recommend to not using it, especially for new integrations of Intelligent Adaptive Authentication.

Deprecated parameter for generating secure challenges

The templateNumber field for generating challenges in Secure Channel mode is now deprecated. While templateNumber is still available, it cannot be combined with any newer features. This deprecation affects the following endpoints:

For more information, see Display content of Secure Channel challenges.

Removed: orchestration-commands endpoint

The POST /orchestration-commands endpoint has now been removed as previously announced. For information about error handling with the Trusted Device microservice and the POST /orchestration-commands-v2 endpoint, see Orchestration Error Handling with Trusted Device microservice and for instructions how to migrate to this microservice, see Migrate to the Trusted Device microservice.

New features and enhancements—supported use cases

OpenID Connect support

The Authentication Component in Intelligent Adaptive Authentication can now be set up to integrate with an OpenID Connect (OIDC) provider, such as Microsoft Entra ID, to use as an external authentication method for single sign-on (SSO). This allows administrative users to authenticate and sign in to the Authentication Component via OIDC or use Digipass authenticators as an additional authentication method to meet multi-factor authentication requirements. If you want to set up and use this feature, contact OneSpan Support.

Pre-provisioned Secure Channel applications

Intelligent Adaptive Authentication now supports pre-provisioned Secure Channel applications for implementations in multi-device licensing mode. The following are elements of the implementation of this new feature.

Support unlocking authenticators in Secure Channel mode

Intelligent Adaptive Authentication now supports  full unlock support for Cronto-based authenticators in Secure Channel mode. When a PIN-based authenticator becomes locked, e.g., because the user enters the wrong PIN too often, the authenticator could be unlocked with an unlock code generated with the POST /authenticators/{serialNumber}/applications/{applName}/unlock endpoint. The generated unlock code was a numerical value in plain text only. Cronto-based authenticators operating in Secure Channel mode, however, require the unlock code to be encoded as a Secure Channel message body, encrypted with the payload key, and transformed into a Cronto image.

Depending on the type of authenticator, you can now select either Plain Text Format for non-Cronto authenticators or Secure Channel Format for Cronto-based authenticators. The endpoint accepts outputFormat as payload and UnlockChallengeInput as input object. The created output depends on the authenticator type to be unlocked:

  • Non-Cronto devices: either do not use this field or enter “outputFormat”: “PlainText".

    The created output will contain the unlockCode field.

  • Cronto-based authenticators: enter “outputFormat”: “SecureChannel".

    The created output will contain the unlockRequestMessage field.

Display content of Secure Channel challenges

For user authentication in Secure Channel mode with a Digipass authenticator, the authenticator has not been displaying any information after the user scanned the Cronto image. The reason is that in Intelligent Adaptive Authentication, the message body was generated by a version of the Secure Messaging SDK Server that did not yet support the showData flag. For transaction validation operations, this flag is already supported and can be set as option when generating the message body but it was not supported for authentication operations because of the integrated version of the Secure Messaging SDK Server.

Now, version 4.34.0 of the Secure Messaging SDK Server has been integrated. Intelligent Adaptive Authentication now supports the authenticator feature to display the challenge title and/or content for message bodies that were generated by the Secure Messaging service or by the Authentication component. With the integration of the newer Secure Messaging SDK Server version, templateNumber is now a deprecated parameter of payloads for generating secure challenges. For more information, see Deprecated parameter for generating secure challenges.

templateNumber and showData are mutually exclusive in the relevant endpoints, i.e., you can use only either templateNumber or showData in your payload!

To generate SecureChallenge payloads with the new method, the showData flag has been added to the options object of the following endpoints:

The introduction of this feature also

  • resolves an issue about the message body with options/formatting: because setting the showData flag is an option, when the message body is customized with options, Intelligent Adaptive Authentication automatically switches to the message body with options/formatting mode.

  • reverts the fix added in Intelligent Adaptive Authentication December Release—22.R4 for POST /users/{userID@domain}/generate-secure-challenge displaying an incorrect message for the title parameter (OAS-10844).

  • fixes support cases CS0067585 and INC0012989 by enabling the authenticator displaying the challenge title and/or content.

The Interactive API Sandbox Reference has been updated accordingly.

Selection of cryptographic application

Intelligent Adaptive Authentication now enables you to select which cryptographic application to use for response validation. When generating challenges for Secure Channel workflows, you can now specify which crypto application will be used to generate the response to the challenge. With this, the selection becomes a regular element of adaptive workflows and enables you to fully control the selection of the crypto app end-to-end and use different authenticator applications.

The cryptoAppIndex and cryptoAppName fields have been added to the payloads of the following endpoints:

cryptoAppIndex: integer, minimum length 1 digit, maximum length 8 digits

cryptoAppName: string, with a length between 1 and 12 characters, which can be uppercase ASCII letters, digits, underscore, or space.

Configurable database connection retry interval and timeout

In the Administration Web Interface of the Authentication component, it is now possible to globally configure the maximum time the connection pool waits to acquire and establish a database connection before the operation is aborted, as well as the delay between consecutive retry attempts. The database Connection Management settings can be configured via the new SERVERS > Global Configuration > Data Store tab.

As this configuration option has been implemented within the Authentication component, we recommend making changes, if any, only in cooperation with our  Support Team, as future deployments of Intelligent Adaptive Authentication may overwrite changes or customized configuration settings.

Applicable authenticator applications processed in defined order

The Applicable DIGIPASS > Application Names policy setting of the Authentication component restricts which authenticator applications are considered for authentication. Previously, these applications were processed in alphabetical order but now are treated as an ordered list. Hence, if multiple authenticator applications are eligible, they are processed in the order defined in the policy. The list order of the relevant authenticator applications can be changed in the Administration Web Interface of the Authentication component.

As this configuration option has been implemented within the Authentication component, we recommend making changes, if any, only in cooperation with our  Support Team, as future deployments of Intelligent Adaptive Authentication may overwrite changes or customized configuration settings.

Improved logging for message delivery

For messages delivered with the Message Delivery Component of the Authentication component, logging has been improved. Concise log messages that contain useful information such as a relevant error  information and the required context are now provided in specific information messages. This improves support for Push Notification and email delivery.

Improvements for database connections

The reconnection and failover mechanisms for database connections have been improved. This enhances performance and reliability for release promotions and database connections in general.

Application index shown for each authenticator application

The Administration Web Interface of the Authentication component now displays the application index of each authenticator application in the corresponding application tab. The application index is dynamically created during the import of the DIGIPASS export file (DPX), based on the order of authenticator applications in this file. Via the application index, the authentication endpoints allow to specify an authenticator application for the request. This option may also be exposed to end users, depending on the client application.

Invalidate administrative sessions on password change

It is now possible to configure automatic invalidation of administrative sessions when the static password of the corresponding user account is changed. By default, session invalidation on password changes is enabled.

Wildcard character configuration for user search

In the Authentication component, it is now possible to globally configure how the Administration Web Interface should handle wildcard characters when searching for users by user name, user ID, or email (via FIND on the home page or the Find/Manage User page):

  • Auto

    The default value. Treats the search term as a partial match pattern and automatically adds wildcard characters before and after it (same behavior as in previous versions).

  • Manual

    Allows you to manually add wildcard characters.

  • Off

    Wildcard characters cannot be used at all and the search returns only exact matches.

The Wildcards setting can be configured via the new SERVERS > Global Configuration > Administration tab (replacing the previous Session Management tab). The View Global Configuration Options administrative privilege is now explicitly granted, and the global configuration can be viewed by any administrative user.

As this configuration option has been implemented within the Authentication component, we recommend making changes, if any, only in cooperation with our  Support Team, as future deployments of Intelligent Adaptive Authentication may overwrite changes or customized configuration settings.

Server data migration task now scheduled to run on any server

The server data migration task now runs with the server mode set to Any, allowing it to be picked up by any server in environments with multiple server instances that share a database. This improves data migration stability following a Intelligent Adaptive Authentication release promotion.

New authenticator status flag to enable or disable authenticators

You can now set the authenticator status, that means explicitly enable or disable an authenticator. If an authenticator is disabled, it cannot be used for regular user operations, such as authentication, administrative logon, transaction data signature validation, or provisioning requests. If you disable an authenticator license, users cannot create new authenticator instances with that license. When authenticator records are imported, they are enabled by default. The authenticator status can be set in the authenticator properties by administrative users with the Update DIGIPASS privilege.

As this configuration option has been implemented within the Authentication component, we recommend making changes, if any, only in cooperation with our  Support Team, as future deployments of Intelligent Adaptive Authentication may overwrite changes or customized configuration settings.

Fixes and other changes

Issue OAS-21699: Misleading audit message when authenticator type limit is reached

Description: When an authenticator could not be assigned during provisioning because the policy's assignment limit for this authenticator type had already been reached, the request failed. However, the corresponding audit message incorrectly indicated that multiple Digipass authenticators were found where a single one was required.

Status: This issue has been fixed. If provisioning fails because of the authenticator type limit, the audit message now provides a more meaningful reason (“The DIGIPASS type limit has been reached“).

Issue OAS-30058 (Support case INC0015050): Avoid initial time synchronization settings can lead to rejected OTPs

Description: The Avoid Initial Time Synchronization policy setting allows to skip the initial time shift initialization on the server side when an authenticator is used for the first time (by effectively using either Identification Time Window or Signature Time Window instead of the Initial Time Window value for the initial synchronization). This can be useful for software authenticators, because the time shift is usually handled by the mobile app. Depending on the values of the DIGIPASS synchronization window settings, this can occasionally cause issues with validating OTPs and lead to rejected authentications.

Status: This issue has been fixed. If Avoid Initial Time Synchronization is set to Software DIGIPASS only, the initial synchronization time window is now set to 1 minute.

Issue OAS-30640 (Support case INC0015446 - PRB0040769): Wrong authenticator instance used for changing PIN

Description: When the Change PIN-scenario was run, using the Orchestration SDK, the wrong authenticator instance was used to validate a one-time password that was not meant to be validated.

Status: This issue has been fixed. Now, the Orchestration SDK addresses the correct authenticator instance, and Intelligent Adaptive Authentication uses the correct instance to change the PIN.

Issue OAS-31946 (Support Case-PRB0040852): User and authenticator counts available again

Description: With the previous database system, performance degradation for analyzing recent activity was fixed by removing functionality to count users and authenticators.

Status: With the migration to a new database system in a previous version, this issue does not occur anymore, and the functionality has been added again. It is now possible again to count the numbers of users and authenticators for Intelligent Adaptive Authentication.

Issue OAS-32300 (Support case CS0207587): Misaligned checkboxes and labels on Admin Privilege tab

Description: In the Administration Web Interface of the Authentication component, when editing a user account’s administrative privileges on the USER > Admin Privileges tab, a layout issue caused checkboxes and their labels to be displayed on separate lines.

Status: This issue has been fixed.

Issues OAS-32408, OAS-32788, OAS-32841, OAS-33344 (Support Case INC0015761): Database timeouts resulted in incorrect error response

Description: In version 25.R2, the internal timeout for the database was reduced to 5 seconds. This would occasionally result incorrectly in a 500 Internal error, sub service failure, server crash error response.

Status: In versions 26.R1 and 26.R2, a number of endpoints have been updated. Now, the remaining endpoints have also been updated. For the following endpoints, if the database runs into a timeout, Intelligent Adaptive Authentication now returns the 504 Gateway timeout HTTP status code.

Issue OAS-32392: Improved error handling to account for slow responses from the Risk Management component

Description: The Risk Management component sometimes experiences database slowness and outages. Because adjusting the read timeout did not sufficiently mitigate the occurrence of generic HTTP 500 errors, a new, dedicated error—504 Gateway Timeout—has been introduced to handle slow responses from the Risk Management component for the following endpoints:

Issue OAS-32533: Incorrect error returned during FIDO2 authentication operations

Description: After an initial fix in the previous version, Intelligent Adaptive Authentication still incorrectly returned 500 Internal Server Error, when the associated downstream configuration service rejected a request during FIDO2 authentication operations. The service rejected the request as invalid, typically an HTTP-400 status code, because the FIDO2 server did not distinguish bad-request errors from other failures when fetching the relying party configuration.

Status: This issue has been fixed, Intelligent Adaptive Authentication now correctly returns the 400 Bad Request error with the specific error message from the configuration service, instead of the generic 500 Internal Server Error.

Issue OAS-32972 (Support case INC0016046): FIDO2 error message too generic

Description:  When a FIDO2 processing conflict occurred, the error message that Intelligent Adaptive Authentication returned for status 409 was too generic. This made it difficult to understand and resolve the issue.

Status: This issue has been fixed. Now an error message with more specific reasoning for the problem is returned.

Issue OAS-33022: Domain list not refreshed when creating a new domain

Description: In the Web Administration Interface of the Authentication component, a UI issue occurred when adding a new domain via Add Domain via the Domain list. After adding the domain details on the Add New Domain page and submitting the entries, you stay on the same page to add more domains, if required. When you return to the Domain list by selecting Click here to return to the previous page, you are taken back to the Domain list. The issue prevented newly created domains from being displayed in the list until the page was refreshed.

Status: This issue has been fixed.

Issue OAS-33573: User names not correctly parsed

Description: When a user name contained more than one at sign (@), Intelligent Adaptive Authentication failed to parse it correctly, resulting in an error. This occurred because domain names containing an at sign were not supported.

Status: This issue has been fixed. Intelligent Adaptive Authentication now correctly parses user names that contain multiple at signs. For all endpoints with userID@domain in the path, the userID part can now include one or more at signs.

Fixed vulnerabilities

As part of our continuous security and maintenance efforts, this release contains updates to third-party components and dependencies. If a vulnerability is identified that materially impacts customers, we will communicate the details directly to affected customers and/or publish relevant guidance in our Knowledge Base.

Known issues

Issue OAS-15853: Incorrect error message when transaction amount fields are provided as data type number

Description: The POST /users/{userID@domain}/transactions/validate endpoint returns an incorrect error message if the transaction amount field is provided from the number data type, and if the transaction amount is large. In this case, the endpoint should return the error message Invalid value type, because the transaction amount field was provided as a number and not as a string. Instead, it returns the incorrect error message Amount: Value must follow -^-?[0-9]{1,20}(\\.[0-9]{1,3})?$,.

Solution: The transaction amount fields in the request body of the transactions/validate endpoint need to be provided as a string. Ensure that the value in the JSON request body is wrapped in double quotes.

Orchestration SDK—supported versions

Intelligent Adaptive Authentication supports the following versions of the Orchestration SDK Client:

  • 5.13.0

  • 5.12.0

  • 5.11.0

  • 5.10.0

  • 5.9.0

  • 5.8.1

  • 5.8.0

  • 5.7.0

  • 5.6.4

  • 5.6.3

  • 5.6.0

  • 5.5.1

  • 5.4.2

  • 5.4.1

  • 5.4.0

  • 5.3.1

  • 5.3.0