OneSpan Mobile Application Shielding

https://docs.onespan.com/mobile/docs
Admin
OneSpan Mobile Application Shielding provides robust security solutions to protect mobile...
Tokens:752,266
Snippets:7,284
Trust Score:10
Update:11 months ago
Show doc for...
Tokens:
Raw
### Authenticator Instance Activation Response Example

Source: https://docs.onespan.com/mobile/docs/integrate-two-step-activation

An example of the XML response for a successful authenticator instance activation. This demonstrates the correct formatting and attribute usage as defined by the DTD.

```xml
<?xml version="1.0"encoding="UTF-8"?>
<DP4Mobile retCode="0"message="Operation Successful" serverTime="1271862050" >
<InstanceActivationinstanceActivationMessage="65464646..." />
</DP4Mobile >
```

--------------------------------

### Install Docker on Ubuntu Desktop

Source: https://docs.onespan.com/mobile/docs/otv-insg-installation-onespan-threat-view-evaluation-package-1-1

Install Docker using the snap package manager on Ubuntu Desktop. This command ensures Docker is installed and available for use.

```bash
sudo snap install docker
```

--------------------------------

### Runtime Data Evaluation Examples

Source: https://docs.onespan.com/mobile/docs/mas-features-mobile-authenticator-studio-actions

Provides examples of data that can be evaluated at runtime for authenticator actions, such as version, rooting status, and serial number.

```text
Supported runtime data| Example
version | 440 (for 4.4.0)
rootingStatus | 0 (Not Rooted) 1 (Rooted)
serialNumberSuffix | 1000000 (for VDS1000000)
```

--------------------------------

### Convert XML Files via Command Line (Java)

Source: https://docs.onespan.com/mobile/docs/mas-4x-cg-reuse-former-customization-file-4-30-10

This command-line interface allows you to convert older Mobile Authenticator Studio XML configuration files to the latest version. It requires Java to be installed and specifies input and output directories for the conversion process. The original file formatting and comments will be lost.

```bash
java –jar lib/xmlconverter.jar –inputFolder xml_input_folder –outputFolder xml_output_folder
```

--------------------------------

### Navigate to Docker Compose Folder

Source: https://docs.onespan.com/mobile/docs/otv-insg-installation-onespan-threat-view-evaluation-package-1-1

Change the current directory to the docker-compose folder within the OneSpan Threat View installation directory. This is a necessary step before running deployment scripts.

```bash
cd ./onespan-threat-view_<version>/docker-compose
```

--------------------------------

### Example: Obfuscate All Classes in a Package

Source: https://docs.onespan.com/mobile/docs/oapps-iga-configuration-of-shielding-tool-rules-on-android-8-1-1

This example demonstrates a simple rule to apply obfuscation to all classes within a specified package. It uses a wildcard to match all classes in 'com.example.app'.

```plaintext
obfuscate class com.example.app.*;
```

--------------------------------

### Callback URL Example for Secure Channel

Source: https://docs.onespan.com/mobile/docs/mas-4x-ig2sa-integrate-app-to-app-secure-channel-communication-4-30-10

An example of a callback URL for the app-to-app Secure Channel process, demonstrating how to handle success responses with a signature. This URL needs to be properly encoded.

```url
dpnopin://app2app_secure_channel?x-success=http://10.10.10.10:8080/TestServer/test.jsp?action=success&signature=%_OTP_%&x-error=http://10.10.10.10:8080/TestServer/test.jsp?action
```

--------------------------------

### Example GET Request for Configuration Update

Source: https://docs.onespan.com/mobile/docs/oapps-ig-integrate-the-automatic-configuration-update-overview-720-705

This example demonstrates an HTTP GET request sent by the App Shielding client to fetch an updated configuration file. It includes essential headers like 'Host', 'If-Modified-Since', and 'X-update-custom-id' for server interaction and caching.

```http
GET /new_config.dat?dev=Samsung&mod=SM-G950F&pkg=com.example.myapp HTTP/1.1
Host: config-update.example.com
If-Modified-Since: Mon, 21 Jan 2019 12:00:00 GMT
X-update-custom-id: fb14234c73e0b9d8e68dc3932a3cfb3ce7982fdc
```

--------------------------------

### Unzip and Navigate Simulator Archive for Event Simulator

Source: https://docs.onespan.com/mobile/docs/otv-igd-installation-of-onespan-threat-view-1-0

This snippet shows how to navigate to the simulator subfolder and extract its contents, preparing for the Event Simulator setup.

```bash
cd ../simulator
for TAR in ./images/*.tar; do docker load -i "$TAR"; done
```

--------------------------------

### Configure URL Settings for Mobile Authenticator Studio

Source: https://docs.onespan.com/mobile/docs/url

This snippet demonstrates how to configure URL settings for Mobile Authenticator Studio. It includes examples for setting the URL, HTTP method, content type, and payload parameters. The POST method requires PayloadParameter elements, while GET requests ignore them. Ensure adherence to URL encoding standards.

```xml
<URL value="http://MY_DOMAIN_NAME/" />
<URL method="POST" contentType="text" value="http://MY_DOMAIN_NAME/...">
  <PayloadParameter key="parameter" value="value" />
  <PayloadParameter key="serial" value="%_SerialNumber_%"/>
  <PayloadParameter key="otp" value="%_OTP_%" />
</URL>
```

--------------------------------

### Run Event Simulator Deployment Script

Source: https://docs.onespan.com/mobile/docs/otv-insg-installation-onespan-threat-view-evaluation-package-1-1

Optionally, run this script to deploy the event simulator, which is useful for testing and simulating events within the Threat View environment.

```bash
./run_simulator.sh
```

--------------------------------

### Example GET Request for Configuration Update

Source: https://docs.onespan.com/mobile/docs/oapps-ig-integrate-the-automatic-configuration-update-overview-731a-721

This code snippet demonstrates an example HTTP GET request made by App Shielding to fetch an updated configuration file. It includes relevant headers like 'Host', 'If-Modified-Since', and 'X-update-custom-id'. The server hosting the configuration must respond with a 200 status code and a valid, signed, and decrypted payload.

```http
GET /new_config.dat?dev=Samsung&mod=SM-G950F&pkg=com.example.myapp HTTP/1.1
Host: config-update.example.com
If-Modified-Since: Mon, 21 Jan 2019 12:00:00 GMT
X-update-custom-id: fb14234c73e0b9d8e68dc3932a3cfb3ce7982fdc

```

--------------------------------

### POST /provisioning/activate

Source: https://docs.onespan.com/mobile/docs/dsapp-sdk-ig-workflow-activation-with-the-sdk-4-34-0

Initiates the activation process by sending client-side information to the provisioning server.

```APIDOC
## POST /provisioning/activate

### Description
This endpoint is called by the client application to request activation data from the provisioning server. It transmits necessary client-side cryptographic material and user identity for the server to validate and generate activation data.

### Method
POST

### Endpoint
/provisioning/activate

### Parameters
#### Path Parameters
None

#### Query Parameters
None

#### Request Body
- **client_ephemeral_public_key** (string) - Required - The public key generated by the client for ephemeral key exchange.
- **client_evidence_message** (string) - Required - A message generated by the client to prove its participation in the key negotiation.
- **user_identity** (string) - Optional - The identity of the user initiating the activation, used for identification purposes.

### Request Example
```json
{
  "client_ephemeral_public_key": "<client_public_key_here>",
  "client_evidence_message": "<client_evidence_message_here>",
  "user_identity": "user123"
}
```

### Response
#### Success Response (200)
- **server_evidence_message** (string) - The message generated by the provisioning server for client-side validation.
- **encrypted_activation_data** (object) - The encrypted data required for activation. May contain multiple sets for different data types (e.g., XFAD, XERC).
  - **data** (string) - The actual encrypted data.
  - **encryption_counter** (integer) - The counter used during encryption for this data set.
  - **mac** (string) - The Message Authentication Code for this data set.

#### Response Example
```json
{
  "server_evidence_message": "<server_evidence_message_here>",
  "encrypted_activation_data": [
    {
      "data": "<encrypted_xfad_here>",
      "encryption_counter": 1,
      "mac": "<mac_for_xfad_here>"
    },
    {
      "data": "<encrypted_xerc_here>",
      "encryption_counter": 2,
      "mac": "<mac_for_xerc_here>"
    }
  ]
}
```
```

--------------------------------

### Example TransactionDataSigningAction - XML

Source: https://docs.onespan.com/mobile/docs/notifications-list-popup

An example of a TransactionDataSigningAction element demonstrating how to use the %_UserIdentifier_% mask in the 'name' attribute to personalize the action's description. This is useful for displaying context-specific information to the user.

```xml
1. <TransactionDataSigningAction id="tds" name="Login request for %_ UserIdentifier_%" ...>
2. ...
3. </TransactionDataSigningAction>
```

--------------------------------

### Example XML Registration Response

Source: https://docs.onespan.com/mobile/docs/advanced-provisioning-protocol

Provides a concrete example of an XML registration response from the server to the Mobile Authenticator Studio, demonstrating the structure and attribute usage for a successful operation.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<DP4Mobile retCode="0" message="Operation Successful" serverTime="1271862050" >
  <Activation xfad="3806564453974A59302DD7..." xerc="55420849628260..." userId="myusername" challenge="123456" serverPublicKey="5431..." initialVector="98752..." nonces="24421..." />
</DP4Mobile>
```

--------------------------------

### Example SecureChannelAction - XML

Source: https://docs.onespan.com/mobile/docs/notifications-list-popup

An example of a SecureChannelAction element showcasing the usage of the %_UserIdentifier_% mask within the 'name' attribute. Similar to TransactionDataSigningAction, this allows for dynamic and personalized naming of secure channel actions.

```xml
1. <SecureChannelAction id="sa" name="Login request for %_UserIdentifier_%" ...>
2. ...
3. </SecureChannelAction>
```

--------------------------------

### Launch Customization Tool (Windows)

Source: https://docs.onespan.com/mobile/docs/customization-tool-via-command-line

Command to open the Mobile Authenticator Studio Customization Tool in a Windows terminal. It specifies the Java properties, classpath including necessary JAR files, and the main class to launch.

```bash
java -Djava.util.logging.config.file=core/logging.properties -cp lib\vasco\dp4mobile-tools.jar;lib\vasco\UtilitiesSDK.jar;lib\ant\ant.jar com.vasco.dp4mobile.customization.launcher.LauncherCMD
```

--------------------------------

### Android App Shielding Activity Guard Setup

Source: https://docs.onespan.com/mobile/docs/oapps-iga-android-integration-on-android-8-0-2

This guide explains how to enable task hijacking protection in Android applications using App Shielding. It involves adding the ShieldSDK-activity-guard.aar library as a dependency.

```bash
To enable this, you need to add the ShieldSDK-activity-guard.aar library as a dependency of the app. This dependency, in combination with shielding the application throu...
```

--------------------------------

### Example Successful Transaction Validation Response (XML)

Source: https://docs.onespan.com/mobile/docs/ig-two-step-activation-transaction-data-signing

An example of a successful XML response from the transaction validation web service. It includes a return code of '0' and a success message, along with an optional confirmation code.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<DP4Mobile retCode="0" message="Operation Successful" confirmationCode="123456" >
  <PendingTransactions/>
</DP4Mobile >
```

--------------------------------

### Launch Customization Tool with Android Parameters (Linux/macOS)

Source: https://docs.onespan.com/mobile/docs/customization-tool-via-command-line

Command to launch the Customization Tool with specific parameters for Android customization. This includes enabling Android customization, setting binary names, keystore passwords, certificate details, and AAB signature options.

```bash
java -Djava.util.logging.config.file=core/logging.properties -cp lib/vasco/dp4mobile-tools.jar:lib/vasco/UtilitiesSDK.jar:lib/ant/ant.jar com.vasco.dp4mobile.customization.launcher.LauncherCMD -customizationAndroid true -binaryName MY_APP -androidKeystorePassword myApkKeystorePassword -androidCertificateName myApkCertificateName -androidCertificatePassword myApkCertificatePassword -androidAabSignatureEnabled true -androidAabKeystorePassword myAabKeystorePassword -androidAabCertificateName myAabCertificateName -androidAabCertificatePassword myAabCertificatePassword
```

--------------------------------

### File Verification Examples

Source: https://docs.onespan.com/mobile/docs/oapps-ig-configuration-of-shielding-tool-rules-on-android-7-3-1-a

Demonstrates how to use the 'verify' command with different patterns to match files. Supports exact matches, wildcard matching for directories and specific file types, and matching all files.

```shell
# Verify a single file
verify "assets/my-asset.bin";

```

```shell
# Verify all files in the assets folder
verify "^assets/.*";

```

```shell
# Verify all HTML/JS in the assets folder
verify "^assets/(.+)\.(html|js)$";

```

```shell
# Verify all files inside the APK
verify ".*";

```

--------------------------------

### Example Successful Transaction Rejection Response - XML

Source: https://docs.onespan.com/mobile/docs/ig-two-step-activation-transaction-data-signing

This XML example shows a successful response from the transaction rejection web service. It includes the root element 'DP4Mobile' with a 'retCode' of '0' and a 'message' indicating 'Operation Successful'.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<DP4Mobile retCode="0" message="Operation Successful" >
  <PendingTransactions />
</DP4Mobile >
```

--------------------------------

### Example XML Registration Response

Source: https://docs.onespan.com/mobile/docs/mas-4x-igsa-standard-secret-exchange-encryption-4-30-10

An example of a valid XML registration response from the server to Mobile Authenticator Studio. This includes the root element DP4Mobile with essential attributes like retCode and message, and the Activation element with its attributes.

```xml
<?xml version="1.0"encoding="UTF-8"?>
<DP4Mobile retCode="0"message="Operation Successful" serverTime="1271862050" >
<Activation xfad="3806564453974A59302DD7..." xerc="55420849628260..."userid="myusername" challenge="123456" />
</DP4Mobile>
```

--------------------------------

### Configure Data Signing Action with QR Input

Source: https://docs.onespan.com/mobile/docs/action

Sets up a data signing action using a specified crypto application, with data input handled via QR code. It defines fields for source account, destination account, and transfer amount, and includes output data settings with a timeout.

```xml
<Action id="sg"cryptoAppIndex="2" actionTrigger="both">
  <InputData inputType="image"imageFormat="all" />
  <OutputData displayed="true"timeout="30" centered="true" />
  <View title="Signature">
    <MenuItem value="Signature"icon="signature.png" />
    <Fields>
      <Field id="DataField1"name="Source account"comment="Enter the source account." />
      <Field id="DataField2"name="Destination account"comment="Enter the destination account." />
      <Field id="DataField3"name="Amount to transfer"comment="Enter the amount to transfer." />
    </Fields>
  </View>
</Action>
```

--------------------------------

### Customize Action Names with Masks - XML Example

Source: https://docs.onespan.com/mobile/docs/notifications-list-popup

This XML-based example illustrates how to customize action names by using placeholders or masks. It shows how dynamic data like serial numbers, user identifiers, or custom attributes can be inserted into the 'name' attribute of an action element.

```xml
Mask| Value
%_SerialNumber_%|  This is the serial number.
%_UserIdentifier_%| This is the user identifier.
%_<custom attribute>_%| The mask is the key of a custom attribute found in the notification. The value will be replaced by the associated value of the custom attribute in the notification. Several custom attributes can be used.
```

--------------------------------

### Start Root Detection Analysis (s method)

Source: https://docs.onespan.com/mobile/docs/root-detect-sdk-integration-guide-4-31-0

Initiates the device analysis to detect rooting or jailbreaking. As of version 4.4, it also verifies the signature file version, requiring it to be higher than a specified threshold. This method is crucial for security checks.

```java
public static boolean s() {
    // Implementation to start analysis
    // Returns true if analysis is successful, false otherwise
}
```

--------------------------------

### Initiate Activation with Orchestration SDK

Source: https://docs.onespan.com/mobile/docs/orch-sdk-ig-activation-5-11-0

This code demonstrates initiating the activation process within the Customer Mobile Application using the Orchestration SDK's `startActivation` method. This is typically called after the user enters their credentials.

```javascript
orchestrationSDK.startActivation({
  userId: 'userIdentifier',
  activationPassword: 'activationPassword'
});

```

--------------------------------

### Run Threat View Deployment Script

Source: https://docs.onespan.com/mobile/docs/otv-insg-installation-onespan-threat-view-evaluation-package-1-1

Execute the main shell script to deploy the Threat View services. This script handles extracting image files and setting up the Docker Compose environment.

```bash
/run_threat-view.sh
```

--------------------------------

### Start Device Analysis with 's' Method

Source: https://docs.onespan.com/mobile/docs/root-detect-sdk-integration-guide-4-30-0

The 's' method initiates the device analysis process to detect rooted or jailbroken devices. It also checks the signature file version against the SDK's requirements. This method is crucial for assessing device integrity.

```java
/**
 * Starts the analysis process to detect whether a device is rooted or jailbroken.
 * As of version 4.4 of the Root Detection SDK, this method also checks the version of the signature file.
 * The signature file version must be higher than the SDK's requirement.
 */
public static void s() {
    // Implementation details for starting analysis
}
```

--------------------------------

### Load Docker Images for Event Simulator

Source: https://docs.onespan.com/mobile/docs/otv-insg-installation-onespan-threat-view-evaluation-package-1-1

Loads Docker images specifically for the Event Simulator from .tar files within the 'images/simulator' subdirectory. This is part of the optional Event Simulator deployment.

```bash
for TAR in ./images/simulator/*.tar; do docker load -i "$TAR"; done
```

--------------------------------

### POST /MY_WEB_SERVICE

Source: https://docs.onespan.com/mobile/docs/mas-4x-igsa-standard-secret-exchange-encryption-4-30-10

This endpoint is used for post-activation requests. It can be configured to use either HTTP GET or POST methods to retrieve activation data. The URL can include various parameters for identifying the user and device.

```APIDOC
## POST /MY_WEB_SERVICE

### Description
This endpoint is called by the Mobile Authenticator Studio after activation to retrieve necessary data. The URL and method (GET/POST) are configurable.

### Method
GET or POST (configurable)

### Endpoint
http://MY_DOMAIN_NAME/MY_WEB_SERVICE

### Parameters
#### Query Parameters
- **registrationIdentifier** (string) - Required - The identifier provided by the user via the online activation screen.
- **otp** (string) - Required - A one-time password generated by the cryptographic application.
- **deviceIdentifier** (string) - Required - The device-unique identifier.
- **version** (string) - Optional - The version of the application binary.
- **UserIdentifier** (string) - Optional - An extra user identifier.
- **DerivationCode** (string) - Optional - Used to bind the authenticator BLOB on the server.
- **RootingStatus** (boolean) - Optional - Indicates whether the device is rooted.

### Request Example
```xml
<URL method="GET" value="http://MY_DOMAIN_NAME/MY_WEB_SERVICE?registrationIdentifier=%_RegistrationIdentifier_%&amp;otp=%_OTP_%&amp;deviceIdentifier=%_DeviceIdentifier_%&amp;version=%_Version_%" />
```

### Response
#### Success Response (200)
- **retCode** (string) - Required - The return code associated with the post-activation request. 0 means success.
- **message** (string) - Required - The return message associated with the request.
- **serverTime** (string) - Optional - The current server GMT time.
```

--------------------------------

### Customize Notification List Popup - React Example

Source: https://docs.onespan.com/mobile/docs/notifications-list-popup

This React code snippet demonstrates how to structure the components for a notification list popup. It shows the nesting of components like Notifications, View, NotificationRegistration, and NotificationsList, allowing for customization of the popup's title.

```jsx
1. <Notifications>
2.   <View />
3.   <NotificationRegistration />
4.   <NotificationsList title="Select notification">
5.     ...
6.   </NotificationsList>
7. </Notifications>
```

--------------------------------

### Configure Web Browsing Action

Source: https://docs.onespan.com/mobile/docs/action

Configures a simple web browsing action, potentially for promotional content. It specifies an output URL and a view for 'Promo' with an associated icon.

```xml
<Action id="promo">
  <OutputData >
    <URLvalue="http://MY_DOMAIN_NAME/..." />
  </OutputData >
  <View title="promo">
    <MenuItem value="Promo"icon="news.png" />
  </View>
</Action>
```

--------------------------------

### Example Callback URL with Secure Message

Source: https://docs.onespan.com/mobile/docs/mas-5-ig-integrate-app-to-app-sc-communication-5-2-0

An example demonstrating the original URL structure for initiating the app-to-app secure channel communication. This URL includes the scheme, callback endpoints for success, error, and cancel events, and the secure message parameter.

```url
dpnopin://app2app_secure_channel?x-success=  
http://10.10.10.10:8080/TestServer/test.jsp?action=success&signature  
=%_OTP_%&x-error=http://10.10.10.10:8080/TestServer/test.jsp?action  
=error&x-cancel=http:// 10.10.10.10:8080/TestServer/test.jsp?action=  
cancel&secure_message=
```

--------------------------------

### Unzip and Navigate Archive for Threat View Deployment

Source: https://docs.onespan.com/mobile/docs/otv-igd-installation-of-onespan-threat-view-1-0

This snippet demonstrates how to unzip the Threat View archive and navigate to the relevant subfolder for deployment. It assumes the archive is downloaded and accessible.

```bash
unzip onespan-threat-view_<version>.zip
cd ./onespan-threat-view_<version>/threat-view
```

--------------------------------

### Configure Transaction List Request - XML

Source: https://docs.onespan.com/mobile/docs/integrate-mas-transaction-data-signing

This XML configuration snippet shows how to set up the TransactionList section within the TransactionDataSigningAction element. It specifies the HTTP method (GET in this example) and the URL to retrieve the list of pending transactions, including placeholders for dynamic parameters like serial number and OTP.

```xml
<TransactionDataSigningAction authenticationCryptoAppIndex="1" signatureCryptoAppIndex="2"displayPopup="true">
  <!-- Transactions list URL -->
  <TransactionList>
  <URL method="GET" value="http://MY_DOMAIN_NAME/MY_WEB_SERVICE?serial=%_SerialNumber_%&amp;otp=%_OTP_%&amp;version=%_Version_%" />
  </TransactionList>
  ...
</TransactionDataSigningAction>
```

--------------------------------

### Post-Activation Request Configuration (XML)

Source: https://docs.onespan.com/mobile/docs/mas-4x-igsa-standard-secret-exchange-encryption-4-30-10

Defines the XML structure for configuring post-activation requests in Mobile Authenticator Studio. It specifies settings like cryptoAppIndex, online activation parameters, and the URL for retrieving activation data. The URL can utilize GET or POST methods and supports dynamic parameters.

```XML
<PostActivation binding="false" cryptoAppIndex="1">
  <OnlinePostActivation destroyOnFailure="true" displayMessageOnSuccess="true">
    <!-- URL used to retrieve the activation data -->
    <URL method="GET" value="http://MY_DOMAIN_NAME/MY_WEB_SERVICE?registrationIdentifier=%_RegistrationIdentifier_%&amp;otp=%_OTP_%&amp;deviceIdentifier=%_DeviceIdentifier_%&amp;version=%_Version_%" />
  </OnlinePostActivation>
...
</PostActivation>
```

--------------------------------

### POST /my_domain_name/my_web_service

Source: https://docs.onespan.com/mobile/docs/integrate-two-step-activation

Initiates a license activation request from the Mobile Authenticator Studio to the online license server.

```APIDOC
## POST /my_domain_name/my_web_service

### Description
This endpoint is used by the Mobile Authenticator Studio to activate licenses online. It accepts various parameters to identify and authorize the activation request.

### Method
POST

### Endpoint
`http://MY_DOMAIN_NAME/MY_WEB_SERVICE`

### Parameters
#### Query Parameters
- **action** (string) - Required - Typically set to "licenseActivation".
- **registrationIdentifier** (string) - Required - The identifier provided by the user. Format: Alphanumeric string, limited to 40 characters.
- **authorizationCode** (string) - Optional - The second factor to authorize the request if the registration identifier is predictable. Format: Alphanumeric string, limited to 40 characters.
- **publicKey** (string) - Required - The public key of the device key pair. Format: Hexadecimal string, 132 characters (can be encrypted).
- **initialVector** (string) - Required - A randomly generated initial vector for encryption. Format: Hexadecimal string of 32 characters.
- **Version** (string) - Optional - The version of the application binary.
- **DeviceIdentifier** (string) - Optional - The device-unique identifier. Format: String of 64 hexadecimal characters.
- **RootingStatus** (string) - Optional - Indicates if the device is rooted (true/false).

### Request Example
```json
{
  "action": "licenseActivation",
  "registrationIdentifier": "VDS%_RegistrationIdentifier_%",
  "authorizationCode": "%_AuthorizationCode_%",
  "publicKey": "%_PublicKey_%",
  "initialVector": "%_InitialVector_%",
  "Version": "1.0.0",
  "DeviceIdentifier": "abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890",
  "RootingStatus": "false"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the activation status (e.g., "success", "failed").
- **message** (string) - A message providing details about the activation result.

#### Response Example
```json
{
  "status": "success",
  "message": "License activated successfully."
}
```
```
Tokens:
Raw