Updates and Security

It is important for devices to be able to verify that any information about updates has not been tampered with. In this way devices can ensure that they only use legitimate download files provided by their software supplier.

To enable verification that information is legitimate, responses sent by FlexNet Operations can be signed using a /signed-updates/ REST API. The account owning the devices to be updated requires a public key to validate the signature. This public key can be displayed on the Create an Account page, after an account has been created. For more information about how to display the public key, see Editing an Account or Sub-account.

For detailed information about the security aspect when delivering Updates, see Getting Started with Updates and Insights.