- 09 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
SAROM token configuration
- Mis à jour le 09 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
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.