React Native - Transmit Security Authentication SDK

Add strong authentication with Passkeys to your native iOS and Android applications, while providing a native experience. This describes how to use the React Native module to register credentials and use them to authenticate your users.

About Authentication SDK

This SDK provides a unified solution for implementing both Apple's public-private key authentication for passkeys on iOS and Google's Credential Manager API for passkeys on Android. It enables the integration of FIDO2-based biometric authentication seamlessly into your mobile applications, offering users a native experience instead of a browser-based one. With passkeys, credentials are securely stored by the device, leveraging iCloud Keychain on iOS and Google Password Manager on Android. These credentials are associated with your domain, facilitating secure sharing between your mobile app and website if applicable.

Using this module, you can easily integrate our Authentication SDK into your React Native app for seamless and secure user identity authentication.

Learn more about how you can boost your security with Transmit Security Authentication.

Understand the flow

We recommended that you read more about the verification flow required steps in our iOS documentation and Android documentation

Configure your app

To integrate this module, you'll need to configure an application.

1. From the Applications page, create a new application or use an existing one.
2. From the application settings:
* For Client type , select native
* For Redirect URI , enter your website URL. This is a mandatory field, but it isn't used for this flow.
* Obtain your client ID and secret for API calls, which are autogenerated upon app creation.
* Enable public sign-up if you manage users using an external system (e.g., external identity provider) or if you want to quickly test WebAuthn registration and authentication without first logging in using a different authentication method.
3. Refer to our iOS and Android documentation mentioned above to configure an auth method and associate your domain for Apple and Google.

Example project setup

#### Note: Configuring Google's assetlinks.json and Apple's apple-app-site-association according to the guidelines in our native SDKs documentation and the user-guides provided by Apple and Google can be a challenging task. However, it is crucial to complete this step accurately for both utilizing the example app and configuring your own application. Instead of attempting to configure this example directly, you are welcome to use it just as a code-reference to ensure proper implementation.

1. In your project, navigate to example/src/config.ts and configure the clientId, domain, secret and baseUrl using the configuration obtained from the Transmit portal.
2. Ensure you have all the necessary dependencies by running yarn in both the module's root folder and the example root folder.
3. Run the example app on a real device using Xcode or Android Studio. Alternatively, execute yarn example ios or yarn example android.



> Important Security Note: Never store your secret in a front-end application.
>
> The example app utilizes a mock server to manage communication with the authentication platform. This mock server employs the secret you have specified in example/src/config.ts exclusively for demonstration purposes. It is paramount that you safeguard your secret in a secure and confidential location.

Installation

``sh
npm install react-native-ts-authentication
`

$3


You might need to execute pod install in your project's /ios folder and set your minimum iOS target to 15.0 in your Podfile (e.g platform :ios, 15.0).

* Add project Capabilities as described iOS quick start
* Update YOUR Bundle ID and setup associated domains as described in the iOS quick start

$3

Add to app/build.gradle under repositories

`gradle
repositories {
google()
maven {
url('https://transmit.jfrog.io/artifactory/transmit-security-gradle-release-local/')
}
}
`
#### Note:
As for projects on Gradle 8+ and Kotlin 1.8+ build will fail if the JDK version between compileKotlin and compileJava and jvmTarget are not aligned.


This won't be necessary anymore from React Native 0.73. More on this: https://kotlinlang.org/docs/whatsnew18.html#obligatory-check-for-jvm-targets-of-related-kotlin-and-java-compile-tasks

Usage

$3

#### iOS
1. Open your project's .xcworkspace found under YOUR_PROJECT_PATH/iOS in Xcode.
2. Create a plist file named TransmitSecurity.plist in your Application with the following content. CLIENT_ID is configured in your Transmit server. Make sure the file is linked to your target.

`xml




credentials


baseUrl
https://api.transmitsecurity.io
clientId
CLIENT_ID



`
#### Android
1. Open your Android manifest XML file, usually located at android/app/src/main.
2. Update the strings.xml file in your Application with the following content. The CLIENT_ID should be replaced with your client ID

`xml


"default_application"
"CLIENT_ID"
https://api.transmitsecurity.io

`

`js
import TSAuthenticationSDKModule from 'react-native-ts-authentication';

componentDidMount(): void {
// Setup the module as soon your component is ready
this.onAppReady().catch(e => void e);
}

private onAppReady = async (): Promise => {
TSAuthenticationSDKModule.initializeSDK();

/*
Instead of using Plist and strings.xml, you can initialize the module with parameters:
1. ClientID obtained from the application settings in the Transmit portal
2. Custom Domain - Can be null (or undefined if not using BaseURL)
3. BaseURL - Can be null or undefined. "https://api.transmitsecurity.io" | eu = "api.eu.transmitsecurity.io" | ca = "api.ca.transmitsecurity.io"

TSAuthenticationSDKModule.initialize(
"YOUR_CLIENT_ID"
);
*/
}
`

#### First time authentication (Register a user)
`js
onStartRegistrationProcess = async (): Promise => {
try {
const response = await TSAuthenticationSDKModule.registerWebAuthn(username, displayName);
// use the response.result string to complete a successful registration in your backend.
} catch (error) {
console.error(Error during registration process: ${error});
}
}
`

#### Start the authentication process
`js
onStartAuthenticationProcess = async (): Promise => {
try {
const response = await TSAuthenticationSDKModule.authenticateWebAuthn(username);
// use the response.result string to complete a successful authentication in your backend.
} catch (error) {
console.error(Error authenticating the user: ${error});
}
}
`

#### Sign a transaction
`js
onStartSignTransactionProcess = async (): Promise => {
try {
const response = await TSAuthenticationSDKModule.signWebauthnTransaction(username);
// use the response.result string to complete a signing a transaction in your backend.
} catch (error) {
console.error(Error signing a transaction: ${error});
}
}
`

$3

• For iOS, ensure that you add the necessary permissions to use FaceID in your app's Info.plist file.

• For Android, add the following strings to your app's strings.xml file:

`xml

Authenticate with Biometrics
Use your device biometrics to authenticate.
Cancel

`

#### Register Native Biometrics
`js
onRegisterNativeBiometics = async (username: string): Promise => {
try {
const response = await TSAuthenticationSDKModule.registerNativeBiometrics(username);
// use the response.result string to complete biometrics registration in your backend.
} catch (error) {
console.error(Error signing a transaction: ${error});
}
}
`

#### Authenticate Biometrics
`js
authenticateWithNativeBiometrics = async (username: string): Promise => {
try {
const challenge = this.randomString();
const response = await TSAuthenticationSDKModule.authenticateNativeBiometrics(username, challenge);
// use the response.result string to complete biometrics authentication in your backend.
} catch (error) {
console.error(Error signing a transaction: ${error});
}
}

private randomString = (): string => {
return (Math.random() + 1).toString(36).substring(7);
}
`

$3


`js
onApprovalWebAuthn = async (username: string, approvalData: { [key: string]: string }): Promise => {
try {
const result = await TSAuthenticationSDKModule.approvalWebAuthn(username, approvalData, []);
console.log("Approval result: ", result);
} catch (error: any) {
this.setState({ errorMessage: ${error} });
}
}
`

$3

`js
onApprovalWebAuthnWithData = async (rawAuthenticationData: TSWebAuthnAuthenticationData): Promise => {
try {
const result = await TSAuthenticationSDKModule.approvalWebAuthnWithData(rawAuthenticationData, []);
console.log("Approval result: ", result);
} catch (error: any) {
this.setState({ errorMessage: ${error} });
}
}
`

$3

`js
onApprovalNativeBiometrics = async (username: string) => {
try {
const result = await TSAuthenticationSDKModule.approvalNativeBiometrics(username, challenge);
console.log("Approval result: ", result);
} catch (error: any) {
this.setState({ errorMessage: ${error} });
}
}
`

$3


`js
onRegisterPINCode = async (username: string, pinCode: string): Promise => {
try {
const result = await TSAuthenticationSDKModule.registerPinCode(username, pinCode);
// use result.contextIdentifier to commit the registration
await TSAuthenticationSDKModule.commitPinRegistration(result.contextIdentifier);
} catch (error) {
console.error(Error registering PIN code: ${error});
}
}
`

$3

`js
authenticatePinCode = async (username: string, pinCode: string): Promise => {
try {
const result = await TSAuthenticationSDKModule.authenticatePinCode(username, pinCode);
// use the result string to complete PIN authentication in your backend.
} catch (error) {
console.error(Error authenticating with PIN code: ${error});
}
}
`

$3

#### Get Device Info
`js
onGetDeviceInfo = async (): Promise => {
try {
const response = await TSAuthenticationSDKModule.getDeviceInfo();
} catch (error) {
console.error(Error getting device info: ${error});
}
}
`

#### Check if the device supports webAuthn
`js
onIsWebAuthenSupported = async (): Promise => {
try {
const isSupported = await TSAuthenticationSDKModule.isWebAuthnSupported();
} catch (error) {
console.error(Error checking if the device supports webAuthn: ${error});
}
}
``

Important Notes

1. Please take note that the example application uses a client-side mock server. In a production environment, a real server is required. Additionally, it is crucial to emphasize that storing the client secret in your front-end application is strictly discouraged for security reasons.

Support

Email us for support

Author

Transmit Security, https://github.com/TransmitSecurity

License

This project is licensed under the MIT license. See the LICENSE file for more info.