Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Tauri Plugin Secure Element
A Tauri plugin for secure element functionality on iOS (Secure Enclave) and Android (Strongbox and TEE).
Features
- Generate secure keys using hardware-backed secure storage
- Sign data with keys stored in secure elements
- List and manage secure keys
- Check secure element support on the device
- Support for biometric and PIN authentication modes
- Cross-platform support for iOS and Android
Installation
npm
# or
# or
Cargo
[]
= "0.1.0"
Setup
Add the plugin to your Rust code in src-tauri/src/lib.rs:
Add the plugin permissions to src-tauri/capabilities/default.json:
Android Biometrics
In order to use biometric protected keys, add this to src-tauri/gen/android/app/build.gradle.kts:
dependencies {
implementation("androidx.biometric:biometric:1.1.0")
}
Note: The src-tauri/gen/android folder is generated by Tauri but should be committed to version control and customized as needed. Once you add the biometric dependency, it will persist across builds (you only need to add it again if you completely regenerate the Android project with tauri android init).
iOS Face ID Permission
Important: For authentication-required keys to work on iOS with Face ID, you must add the Face ID usage description to your iOS Info.plist.
Add to src-tauri/gen/apple/tauri-app_iOS/Info.plist (replace tauri-app_iOS with your app name):
NSFaceIDUsageDescription
This app uses Face ID to authenticate access to your secure keys.
Add this entry anywhere within the <dict> section of the Info.plist file.
Note: Like the Android configuration, the src-tauri/gen/apple folder should be committed to version control. The Face ID permission will persist across builds unless you regenerate the iOS project with tauri ios init.
Touch ID does not require a separate permission entry - it works automatically when Face ID permission is granted or when no biometric hardware is available.
Usage
import {
checkSecureElementSupport,
generateSecureKey,
listKeys,
signWithKey,
deleteKey,
type AuthenticationMode,
} from "tauri-plugin-secure-element-api";
// Check if secure element is supported
const support = await checkSecureElementSupport();
console.log("Secure element supported:", support.secureElementSupported);
// Generate a new secure key
const { publicKey, keyName } = await generateSecureKey(
"my-key-name",
"pinOrBiometric" // or 'none' or 'biometricOnly'
);
// List all keys
const keys = await listKeys();
// Sign data with a key
const data = new Uint8Array([1, 2, 3, 4]);
const signature = await signWithKey("my-key-name", data);
// Delete a key
await deleteKey("my-key-name");
API Reference
checkSecureElementSupport()
Returns information about secure element support on the device.
Returns: Promise<SecureElementSupport>
interface SecureElementSupport {
secureElementSupported: boolean;
teeSupported: boolean;
canEnforceBiometricOnly: boolean;
}
generateSecureKey(keyName: string, authMode?: AuthenticationMode)
Generates a new secure key in the device's secure element.
Parameters:
keyName: Unique name for the keyauthMode: Authentication mode ('none','pinOrBiometric', or'biometricOnly')
Returns: Promise<{ publicKey: string; keyName: string }>
listKeys(keyName?: string, publicKey?: string)
Lists keys stored in the secure element. Can filter by key name or public key.
Returns: Promise<KeyInfo[]>
interface KeyInfo {
keyName: string;
publicKey: string;
requiresAuthentication?: boolean;
}
signWithKey(keyName: string, data: Uint8Array)
Signs data using a key stored in the secure element.
Parameters:
keyName: Name of the key to usedata: Data to sign asUint8Array
Returns: Promise<Uint8Array> - The signature
deleteKey(keyName?: string, publicKey?: string)
Deletes a key from the secure element. At least one parameter must be provided.
Returns: Promise<boolean> - Success status
Platform Support
- iOS: Uses Secure Enclave for key generation and signing
- Android: Uses Strongbox and TEE (Trusted Execution Environment) when available
License
Apache-2.0
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.