Introduction

Device requirements

Android

The SDK relies on the Android Keystore APIs to manage the lifecycle of the key and on the Biometric APIs to handle cryptographic operations.

The Biometric APIs are available since Android 29 but are also available in older versions through the AndroidX Biometric support library.

To use the SDK, the device must meet the following minimum requirements:

• Android API 29 or higher
• Biometric hardware available
• At least one biometric enrolled

The RSS Mobile SDK provides a utility method to validate that the device fits the minimum requirements.

iOS

This guide describes RSS iOS SDK 2.6.0, with examples targeting iOS 16.6. Follow the deployment requirements supplied with your SDK distribution. DSS activation and signing require a physical device with Secure Enclave, a configured device passcode, and enrolled Face ID or Touch ID.

The SDK uses Keychain services and Secure Enclave to manage and protect the DSS key. Check Rss.isDeviceCompliant() before starting a biometric signing flow. Simulator slices are provided for integration work; validate the full signing flow on a physical device.

See iOS Getting started for installation, the Face ID usage description and the iOS compliance result values.

Multi user management

The SDK and all its services support the use of multiple users within the same app. The data storage and keychain entries are separated per user based on the sub attribute of the idToken.

Only one session can be opened for a particular user at a time. This means that a previously opened session will be closed when a new one is started.

On iOS, multiple users can be enrolled, but the underlying SDK has one active user session. Serialize user flows and do not continue using a previous user's service wrappers after switching users.