Backend APIs: Updating device’s display_name input field restrictions

Breaking change.

This announcement was replaced by: https://support.futurae.com/hc/en-us/articles/10146325941522-Backend-APIs-Updating-device-s-display-name-input-field-restrictions-Announcement-update-

What is changing?

Starting on March 1st, further input restrictions are going to be applied to the device resource’s display_name field of the Auth and Admin APIs.

Aiming to further improve the service’s security, the value accepted for this field has to respect the following conditions:

• String (100 characters maximum length) with spaces and case-sensitive letters ([a-zA-Z])
• Numbers ([0-9]) 
• Special characters - + / . ( )

To contextualize this change, the device’s display_name is a string used to identify the authenticator device. More details at https://www.futurae.com/docs/api/admin/#device.

Providing an invalid character to this field when calling the Auth and Admin APIs, will make the request fail with 400 Bad Request.

Existing display_name records that contain invalid characters, will be automatically sanitized by removing the invalid characters.

Does this change have any impact on my Futurae API integration?

This update might require changes on your Futurae Auth and Admin API integration, in order to ensure that the device’s display_name input restrictions are honored by your application. We recommend any necessary changes to be addressed until March 1st to avoid failures when updating the device’s display_name.