Extended MobileID device hash management
We have extended MobileID device hash management with new endpoints in the ReuseID API and added new blocking functionality in the Signicat Dashboard.
There are 27 updates that contain this tag.
View all tagsWe have extended MobileID device hash management with new endpoints in the ReuseID API and added new blocking functionality in the Signicat Dashboard.
We have updated the MobileID, ReuseID, and Admin APIs with new device hash management features and device state event generation parameters.
We have now completely removed the MobileID passport scan feature.
We have extended the set of device risk attributes that can be collected during a transaction. These attributes give you a deeper insight into the state of the device at the time of use.
We have standardised the naming scheme for the cloud backup recovery method, improved concurrency for device requests, and refactored audit event types.
We have deprecated the Get proofings for user endpoint for the User resource in the MobileID API.
We have removed the Get full final result of the passport scan endpoint for the Passport scan resource in the MobileID API.
The MobileID Passport scan feature that was previously deprecated will be completely removed on 01.11.2025.
We have improved our Account recovery feature by adding support for server-side face authentication, making it more user-friendly and secure.
We have removed the lockReason attribute from the device object in the MobileID API.
We have removed the character set limitations for the device name, allowing for the use of any letters, digits, or special characters.
We have removed the obsolete risk attribute isUnknownSourcesEnabled from the MobileID API, Admin API, and Signicat Dashboard.
The signature request parameter signedJwtCertificateOption now no longer supports the values SINGLE or CHAIN in the MobileID API.
The new Face authentication feature introduces a new authentication method that uses server-side biometrics.
The MobileID Passport scan feature is now deprecated, and is replaced by our ReuseID solution.
Risk data is now also returned when the operation completes with an error status or is expired.
The MobileID API has been extended with a new resource for Account recovery.
We have also added a new MobileID event which you can subscribe to, called device.state.change.
We have extended the operationProperties of registration, authentication and signature requests with a new field called requestedUserAttributes.
We have extended all requests and responses containing user data with a new field called segment to allow you to segment end-users and corresponding transactions.
The User resource has been updated to remove the previously deprecated Resolve external reference endpoint, which used the HTTP GET method.
The Device management resource has been extended with endpoints to manage geofencing settings.
Responses for successfully completed MobileID authentication and signature operations have also been extended with a new client data field.
The new Geofencing feature enables you to strengthen security for transactions by evaluating the current location of a device against a list of allowed regions.
We now collect a set of default risk attributes for debugging purposes.
The User resource has been improved with a new POST endpoint to resolve the user ID based on an external reference, replacing the deprecated GET endpoint.
The User resource has been extended with a new endpoint that allows you to get device transactions for all of the end-user's devices.
The Device Management resource has been extended with a new endpoint for retrieving device transactions. Device name length and character set validation has also been added.
The new Passport scan feature allows you to validate the authenticity of an end-user's passport and collect passport attributes.