--- title: "OneSpan Cloud Authentication May Release – 26.R2" slug: "oca-release-notes-may-26r2" updated: 2026-04-09T10:04:14Z published: 2026-04-09T10:04:14Z canonical: "docs.onespan.com/oca-release-notes-may-26r2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # OneSpan Cloud Authentication May Release – 26.R2 ## Important notices ### Stricter user data validation > Breaking change planned for Q3 2026: stricter user data validation 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 OneSpan Cloud 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. This affects the following endpoints: - [PUT /users/{userID@domain}](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/createUserUsingPUT]/sandbox#/Users/userRegisterUsingPOST) - [PATCH /users/{userID@domain}](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/updateUserUsingPATCH) > Existing user info fields are kept as is and are only revalidated when you attempt to update them. ## Deprecated or removed components and services ### Deprecated orchestration authentication option The `Face` option for the login input payload of the [POST /users/{userID@domain}/login](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/loginUsingPOST) endpoint is a legacy option and has been deprecated. Instead, `Fingerprint` should be used. In a future release, a new biometric option will be available. This information has also been added to the endpoint schema description in the [Interactive API Reference](https://community.onespan.com/products/onespan-cloud-authentication/sandbox). ### Orchestration error handling with orchestration-commands endpoint > Orchestration error handling with the [POST /orchestration-commands](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Device Commands/trustedDeviceCmdUsingPOST) endpoint is deprecated and will be removed in version 26.R3 in Q3 of 2026. ## Fixes and other changes Issue OAS-31935: Incorrect error returned when relying party is not found (FIDO2) **Description**: In FIDO2-based authentication operations, OneSpan Cloud Authentication returned an incorrect error, `500 Internal Server Error: "Data cannot be retrieved from external service"`. This occurred when the tenant configuration was missing or had a relying party configured that did not exist. **Status**: This issue has been fixed, OneSpan Cloud Authentication now correctly returns the `409` operation failed error. Issues OAS-32408, OAS-32788 (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 version 26.R1, a first set of endpoints have been updated. Now, another set has 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. - All endpoints of the [Authenticators](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Authenticators) API - All endpoints of the [Users](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users) API - Bulkfile Upload: - [POST /bulkfiles](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Bulkfile%20Upload/uploadBulkfileUsingPOST) - [GET /bulkfiles/{uuid}](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Bulkfile%20Upload/getBulkfileStatusUsingGET) - Provisioning: - [POST /registrations](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/registrationUsingPOST) - [POST /registrations/check-status](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/checkActivationStatusUsingPOST) - [POST /registrations/{registrationID}/activate](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/activateUsingPOST) - [POST /registrations/{registrationID}/add-device](/registrations/{registrationID}/add-device) - [POST /registrations/{registrationID}/generate-ephemeral-key](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/generateEphemeralKeyUsingPOST) - [POST /registrations/{registrationID}/generate-activation-message](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/registrationGenerateActivationMessageUsingPOST) - [POST /users/register](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/userRegisterUsingPOST) - [POST /users/{userID@domain}/authenticators/{serialNumber}/update-pnid](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Provisioning/updateDevicePnidUsingPOST) - Transactions: - [POST /users/{userID@domain}/transactions/validate](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Transactions/transactionValidationUsingPOST) - Users: - [POST /users/register](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/userRegisterUsingPOST) - [POST /users/{userID@domain}/generate-secure-challenge](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/generateSecureChallengeUsingPOST) - [POST /users/{userID@domain}/generate-signing-request](/users/{userID@domain}/generate-signing-request) - [POST /users/{userID@domain}/transactions/validate](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/transactionValidationUsingPOST) - [POST /users/{userID@domain}/sync-authenticator](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/syncAuthenticatorUsingPOST) - [POST /users/{userID@domain}/authenticators/{serialNumber}/update-pnid](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/updateDevicePnidUsingPOST) - [POST /users/{userID@domain}/generate-virtual-signature](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Users/generateVirtualSignatureRequestUsingPOST) - Sessions: - [GET /sessions/{requestID}](/sessions/{requestID}) Fixed vulnerabilities For a detailed list of fixed vulnerabilities, see the relevant Knowledge Base article(s) in our Customer Support Portal. ## 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](https://community.onespan.com/products/onespan-cloud-authentication/sandbox#/Transactions/transactionValidationUsingPOST) 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 OneSpan Cloud Authentication supports the following versions of the Orchestration SDK Client: - 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