Manage soft token SDKs

Use this procedure to configure a custom soft token SDK in IDaaS. After you configure SDK credentials, you can add custom push messages.

Before you begin

Before you configure soft token SDK settings, confirm you have the required provider credentials and files.

• Firebase Cloud Messaging (FCM): JSON service account credentials.
• Google Play Integrity: JSON credentials for your Google Play project (Android custom applications).
• Apple Push Notification service (APNS): P12 certificate file, P12 password, and Apple bundle ID (iOS custom applications).

Configure soft token SDK credentials

1. Click > Policies > Soft Token SDK. The Soft Token SDK settings page appears.
2. Click the SDK Credentials tab.
3. Configure Firebase Cloud Messaging (FCM) for Android and iOS push notifications:
   1. Click to upload the JSON credential file for your FCM project.
   2. Click Save. The Project ID and Client ID fields are populated automatically.
   3. Optional: Click Clear Credentials to clear the project credentials.
4. For Android custom applications, configure Google Play Integrity Credentials:
   1. Click to upload the JSON credential file for your Google Play project.
   2. Click Save.
   3. If required, click Clear Credentials to clear the P12 file password and project bundle.
5. To use Apple Push Notification Service (APNS) for iOS:
   1. Click to upload the APNS file.
   2. Enter the Password for the P12 file.
   3. Enter the Apple Project Bundle ID.
   4. Select Production Mode if your application is in production.
   5. Optional: Select Mutable Content to add the notification app extension flag. For more information, see Apple Developer documentation.
6. Optional: Click Clear Credentials to remove any SDK credentials.
7. Click Save.

Configure custom push messages

1. Click the Push Messages tab. The SDK Push Messages page appears, including a Generic message in the Identifier table.
2. To add a custom push message, do the following:

   1. Click Add. The Add Push Message dialog box appears.

   2. Enter Identifier. Add this same value to the pushMessageIdentifier parameter in your API request. For API usage details, see the Identity as a Service Authentication API Guide.

      note

      To send a custom push message, set pushMessageIdentifier in the API request to match Identifier in SDK settings. If no match is found, the request fails. If you do not set pushMessageIdentifier, the default push message is used. This parameter is optional and case-insensitive.

      To delete the current default push message, first set a different message as default.

   3. Enter the Push Title.

   4. Enter the Push Message.

   5. Optional: Select Set as the default push message.

   6. Click Save.

Validate your changes

After configuration, validate the result.

1. Confirm SDK credential fields are saved and visible after refresh.
2. Send a test push request and confirm delivery on the target device.
3. If using custom push messages, confirm the expected message appears when pushMessageIdentifier is provided.
4. If the message is not as expected, verify identifier matching and default message selection.