SAROM token configuration
  • 09 Jan 2025
  • 1 Minute à lire
  • Sombre
    Lumière
  • PDF

SAROM token configuration

  • Sombre
    Lumière
  • PDF

The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article

The developer has control of the generation of the SAROM encryption key with the mandatory customer-specified token. This configuration option allows the customer to change the key by changing the customer-specific token.

Implementation of the SAROM token configuration

The customer token is set by adding the following item to the App Shielding config.xml file:

config.xml

...
<secureAppROMToken v="RXhhbXBsZSBmb3IgU0xTIGN1c3RvbWVyIHRva2Vu"/>
...

The value of secureAppROMToken is a string. To use binary data for the token, it can be encoded as base64 format.

Implementation details

To enable this feature in an application, the app must integrate the platform specific App Shielding elements, as well as have code to use the features before shielding the app. For more information, see iOS integration and Android integration.


Cet article vous a-t-il été utile ?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Ozzy, facilitant la découverte de connaissances grâce à l’intelligence conversationnelle