Skip to main content
Version: 3.4

Ionic Identity Vault

Ionic Identity Vault is an all-in-one frontend identity management system that combines security best practices and the latest in biometric authentication options available on iOS and Android.

The Vault manages secure user identity and session tokens, ensuring sensitive tokens are encrypted at rest, stored only in secure locations on the device, and unlocked only with biometric identity (TouchID/FaceID).

Without Ionic Identity Vault, Ionic developers have to resort to combining third party Cordova plugins, often resulting in insecure setups due to the lack of correct implementation of biometric and at-rest encryption strategies. Learn more.

Installation#

If you have not already setup Ionic Enterprise in your app, follow the one-time setup steps.

Next, install the plugin:

npm install @ionic-enterprise/identity-vaultnpx cap sync

Update the native project config files:

// iOS - Info.plist<key>NSFaceIDUsageDescription</key><string>Use Face ID to authenticate yourself and login</string>
// Android - No additional changes needed

Reference App#

A complete login/logout experience that includes biometrics (Face ID with passcode as a fallback), secure token storage, background data hiding, and session timeouts.

Configuring the Vault#

The IonicIdentityVaultUser class takes a generic session type which represents the type of the session you'll store in the vault. You can use the DefaultSession or extend the class to create a custom session. In the constructor of your Identity service, the vault is configured by providing options to the super() call:

interface MyCustomSession extends DefaultSession {  // username & token are inherited  email: string;  age: number;  nicknames: string[];}
export class IdentityService extends IonicIdentityVaultUser<MyCustomSession> {
constructor(private http: HttpClient, private router: Router, platform: Platform) {  super(platform, {    authMode: AuthMode.BiometricAndPasscode, // Use biometrics auth with passcode fallback    restoreSessionOnReady: false, // whether or not to immediately attempt to restore the session when the vault is ready    unlockOnReady: false, // set true to auto prompt the user to unlock when vault is ready    unlockOnAccess: true, // set to true to auto prompt the user to unlock on first read access    lockAfter: 5000, // lock after 5 seconds in the background    hideScreenOnBackground: true // when in app launcher mode hide the current screen and display the splashscreen  });
  onVaultUnlocked(config: VaultConfig) {    //Route to my home page  }
  onVaultLocked() {    //Route to my login page  }
  async onPasscodeRequest(isPasscodeSetRequest: boolean) {    // Display a custom Passcode prompt and return the passcode as a string    // or return undefined to use the build in native prompts. isPasscodeSetRequest    // is true when attempting to set a new passcode on the vault, you can use    // it to do something like prompt the user twice for the pin.  }
}

Automatically adding your token to requests#

If you'd like to automatically add your authorization token from your identity service to every request, you can see a simple example at in our demo repo.

Important Note

If you're upgrading from the 3.0.0 to >=3.1.0 versions you no longer need to install 2 packages. The plugin now ships under the @ionic-enterprise/identity-vault package. Simply run the commands below to upgrade. Imports and usage should remain identical.

Upgrading from v3.0.0 to >=v3.1.0#

First, remove v3.0.0 of the plugin:

# NOTE: do not prepend @ionic-enterprise to the plugin name when removing v3.0.0ionic cordova plugin rm cordova-plugin-identity-vault

Make sure @ionic-enterprise/cordova-plugin-identity-vault and cordova-plugin-identity-vault are completely removed from your package.json in all locations.

...  "dependencies": {    ...     // Make sure both of these are gone from the dependencies    "@ionic-enterprise/cordova-plugin-identity-vault": "3.0.0",    "@ionic-enterprise/identity-vault": "3.0.0",    ...  }  "cordova": {    "plugins": {      ...      // Make sure both of these are gone from the cordova plugins section as well      "@ionic-enterprise/cordova-plugin-identity-vault": {},      "cordova-plugin-identity-vault": {}      ...    },    ...  }...

It should now be safe to add >=v3.1.0 of the plugin:

ionic cordova plugin add @ionic-enterprise/identity-vault@latest

API Documentation#

You can find the API and interface documentation for everything below. The main classes to pay attention to are:

  • IonicIdentityVaultUser - Subclass this when creating your identity service.
  • DefaultSession - This is the generic type that represents your session. Extend this to implement a custom session.
  • IdentityVault - This is the lower level vault API. You can use this to implement advanced workflows including multi-tenant vaults.

Index#

Enumerations#

Interfaces#

Type aliases#


Enumerations#

AuthMode#

AuthMode:

The type of authentication the vault should be configured to allow.

BiometricAndPasscode#

BiometricAndPasscode:

Both biometric and passcode authentication should be allowed


BiometricOnly#

BiometricOnly:

Biometrics authentication should only be allowed


BiometricOrPasscode#

BiometricOrPasscode:

Use biometrics if it is available, otherwise use passcode


InMemoryOnly#

InMemoryOnly:

Both biometric and passcode authentication should be disabled. With this setting all data in the vault will be cleared on lock or if the app is closed. Stored data is kept only in memory.


PasscodeOnly#

PasscodeOnly:

Passcode authentication should only be allowed


SecureStorage#

SecureStorage:

Both biometric and passcode authentication will be disabled but any stored values will persist and be stored securely at rest using the keychain and will be available without needing to authenticate via passcode or biometrics when the device is unlocked.



VaultErrorCodes#

VaultErrorCodes:

The meaning of the error code in the thrown VaultError

AuthFailed#

AuthFailed:

User authentication failed


BiometricsNotEnabled#

BiometricsNotEnabled:

The operation failed because biometric authentication is not enabled


InvalidArguments#

InvalidArguments:

The operation failed because the provided arguments were invalid


InvalidAuthMode#

InvalidAuthMode:

The AuthMode is invalid


InvalidatedCredential#

InvalidatedCredential:

The credentials were invalidated. This can happen when a user changes biometrics or passcode.


KeyNotFound#

KeyNotFound:

The key was not found. This can happen when a user changes biometrics or passcode.


MismatchedPasscode#

MismatchedPasscode:

The user provided mismatched passcodes


MissingPasscode#

MissingPasscode:

The operation requires passcode to be setup but it isn't set yet. Call setPasscode to set it.


PasscodeNotEnabled#

PasscodeNotEnabled:

The operation failed because passcode authentication is not enabled


SecurityNotAvailable#

SecurityNotAvailable:

Biometric security is unavailable


TooManyFailedAttempts#

TooManyFailedAttempts:

Too many failed authentication attempts so the vault was cleared an user will need to login again


Unknown#

Unknown:

An unknown error happened


UserCanceledInteraction#

UserCanceledInteraction:

The user cancelled the native authentication dialog


VaultLocked#

VaultLocked:

The operation failed because the vault was locked


VaultUnavailable#

VaultUnavailable:

The operation failed because the vault was unavailable



Interfaces#

DefaultSession#

DefaultSession:

The interface for the Default Session. Extend this interface to make a custom session

usage:

MyCustomSession extends DefaultSession { email: string; age: number; nicknames: string[];}

token#

● token: string


username#

● username: string



IdentityVault#

IdentityVault:

The underlying vault API. You can gain direct access to the vault for more advanced usage by using the IdentityVaultUser.getVault method.

<Optional> config#

● config: PluginConfiguration

The current configuration of the vault will stay current as long as unsubscribe is not called.


clear#

clear(): Promise<void>

Clear all vault data including stored tokens, values, and passcodes. The vault will be empty and unlocked after this.

Returns: Promise<void>


getBiometricType#

getBiometricType(): Promise<BiometricType>

Get the type of biometrics the device supports

Returns: Promise<BiometricType> the type of biometrics the device supports


getConfig#

getConfig(): Promise<PluginConfiguration>

Get the current configuration of the vault

Returns: Promise<PluginConfiguration> the configuration


getToken#

getToken(): Promise<any>

Get any data stored in the token slot. This is equivalent to calling getValue("token").

throws: VaultError - if vault is locked

Returns: Promise<any> token data


getUsername#

getUsername(): Promise<string>

Get the username associated with the vault

Returns: Promise<string> the username for the vault


getValue#

getValue(key: string): Promise<any>

Get a value stored under the given key.

throws: VaultError - if vault is locked

Parameters:

NameTypeDescription
keystringthe key where the value is stored

Returns: Promise<any> the value stored at the key


isBiometricsAvailable#

isBiometricsAvailable(): Promise<boolean>

Check whether or not biometrics is supported by the device and has been configured by the current user of the device

Returns: Promise<boolean> whether or not biometrics is available


isBiometricsEnabled#

isBiometricsEnabled(): Promise<boolean>

Check whether or not biometrics is enabled on the vault

Returns: Promise<boolean> whether or not biometrics is enabled


isInUse#

isInUse(): Promise<boolean>

Check whether the vault has any values stored in it.

Returns: Promise<boolean> whether the vault has stored values


isLocked#

isLocked(): Promise<boolean>

Check whether the vault is currently locked

Returns: Promise<boolean> whether the vault is locked


isPasscodeEnabled#

isPasscodeEnabled(): Promise<boolean>

Check if passcode authentication is enabled for the vault

Returns: Promise<boolean> whether or not the passcode is enabled


isPasscodeSetupNeeded#

isPasscodeSetupNeeded(): Promise<boolean>

Check whether or not a passcode needs to be set for the vault using setPasscode

Returns: Promise<boolean> whether or not the passcode needs to be set


isSecureStorageModeEnabled#

isSecureStorageModeEnabled(): Promise<boolean>

Check if AuthMode.SecureStorage is enabled for the vault

Returns: Promise<boolean> whether or not the secure storage mode is enabled


lock#

lock(): Promise<void>

Lock the vault clearing the contents from memory and requiring biometrics or passcode to unlock

Returns: Promise<void>


remainingAttempts#

remainingAttempts(): Promise<number>

Check how many remaining failed attempts are left until vault clears

Returns: Promise<number> the number of remaining attempts


setBiometricsEnabled#

setBiometricsEnabled(isBiometricsEnabled: boolean): Promise<void>

Enable/Disable Biometric authentication for the vault

throws: VaultError - if biometrics is unavailable or the vault is locked

Parameters:

NameTypeDescription
isBiometricsEnabledbooleanwhether or not biometrics should be enabled

Returns: Promise<void>


setPasscode#

setPasscode(passcode?: string): Promise<void>

Set or Change the passcode for the vault

throws: VaultError - if the vault is locked, passcode is disabled, user canceled pin prompt, or pin was mismatched

Parameters:

NameTypeDescription
Optional passcodestringThe passcode to set. If left null a native dialog will prompt the user to enter it.

Returns: Promise<void>


setPasscodeEnabled#

setPasscodeEnabled(isPasscodeEnabled: boolean): Promise<void>

Enable/Disable passcode authentication for the vault

throws: VaultError - if the vault is locked

Parameters:

NameTypeDescription
isPasscodeEnabledbooleanwhether or not passcode should be enabled

Returns: Promise<void>


setSecureStorageModeEnabled#

setSecureStorageModeEnabled(isSecureStorageModeEnabled: boolean): Promise<void>

Enable/Disable secure storage mode for the vault. Setting AuthMode.SecureStorage automatically disables passcode and biometric authentication and allows for session values to be stored persistently and securely at rest using the keychain but allowing the user to access the data without authenticating as long as the device is unlocked.

throws: VaultError - if the vault is locked

Parameters:

NameTypeDescription
isSecureStorageModeEnabledbooleanwhether or not secure storage mode should be enabled

Returns: Promise<void>


storeToken#

storeToken(token: any): Promise<void>

Store a value securely in the token slot. This is equivalent to calling storeValue("token", token).

throws: VaultError - if vault is locked, or if passcode is enabled but passcode has not been setup

Parameters:

NameTypeDescription
tokenanythe value to store in the token slot

Returns: Promise<void>


storeValue#

storeValue(key: string, value: any): Promise<void>

Store data securely under the given key.

throws: VaultError - if vault is locked, or if passcode is enabled but passcode has not been setup

Parameters:

NameTypeDescription
keystringthe key to store in the value in
valueanythe value to store

Returns: Promise<void>


unlock#

unlock(usingPasscode?: boolean, passcode?: string): Promise<void>

Unlock the vault using either passcode or biometrics

throws: VaultError - if the vault is locked, the unlock type wasn't enabled, user canceled pin prompt, or pin was mismatched

Parameters:

NameTypeDescription
Optional usingPasscodebooleanwhether or not to use passcode to unlock the vault
Optional passcodestringThe passcode to use. If left null a native dialog will prompt the user to enter it.

Returns: Promise<void>


unsubscribe#

unsubscribe(): Promise<void>

Unsubscribe the instance from events about the vault.

Returns: Promise<void>



IdentityVaultUser#

IdentityVaultUser:

The main class which you can extend in order to implement vault usage. @typeparam T must extend DefaultSession

usage:

interface MyCustomSession extends DefaultSession { // username & token are inherited email: string; age: number; nicknames: string[];}
export class IdentityService extends IonicIdentityVaultUser<MyCustomSession> {
constructor(private http: HttpClient, private router: Router, platform: Platform) { super(platform, {   authMode: AuthMode.BiometricAndPasscode,   restoreSessionOnReady: false,   unlockOnReady: false, // set true to auto prompt the user to unlock when vault is ready   unlockOnAccess: true,   lockAfter: 5000, // lock after 5 seconds in the background   hideScreenOnBackground: true });
 onVaultUnlocked(config: VaultConfig) {   //Route to my home page }
 onVaultLocked(event: LockEvent) {   //Route to my login page }
}

getAuthMode#

getAuthMode(): Promise<AuthMode>

Get the AuthMode for the vault.

Returns: Promise<AuthMode>


getBiometricType#

getBiometricType(): Promise<BiometricType>

Get the type of biometrics the device supports

Returns: Promise<BiometricType> the type of biometrics the device supports


getPlugin#

getPlugin(): IonicNativeAuthPlugin

Returns the underlying Plugin Implementation. This can be overriden in the sub class service to allow for a customer browser implementation. Note that when overriding this with a browser implementation you should use the storeValue/getValue functions with the key session to store & retrieve the session as described or by DefaultSession or the interface that extends it.

usage:

getPlugin(): IonicNativeAuthPlugin { if (this.platform.is('cordova')) {   return super.getPlugin(); } // MyCustomerBrowserImplementation must implement the IonicNativeAuthPlugin interface // make sure getValue('session') & storeValue('session') store & retrieve the session. return MyCustomBrowserImplementation();}

Returns: IonicNativeAuthPlugin


getSession#

getSession(): Promise<T | undefined>

getSession(): Promise<T | undefined>

The stored session data

Returns: Promise<T | undefined>

Get the session from memory (without checking the vault for it)

Returns: Promise<T | undefined>


getVault#

getVault(): Promise<IdentityVault>

Get raw access to the underlying vault api

Returns: Promise<IdentityVault>


hasStoredSession#

hasStoredSession(): Promise<boolean>

Check if there are any saved sessions in the vault

Returns: Promise<boolean>


isBiometricsAvailable#

isBiometricsAvailable(): Promise<boolean>

Check whether or not biometrics is supported by the device and has been configured by the current user of the device

Returns: Promise<boolean> whether or not biometrics is available


isBiometricsEnabled#

isBiometricsEnabled(): Promise<boolean>

Check whether or not biometrics is enabled on the vault

Returns: Promise<boolean> whether or not biometrics is enabled


isPasscodeEnabled#

isPasscodeEnabled(): Promise<boolean>

Check if passcode authentication is enabled for the vault

Returns: Promise<boolean> whether or not the passcode is enabled


isSecureStorageModeEnabled#

isSecureStorageModeEnabled(): Promise<boolean>

Check if AuthMode.SecureStorage is enabled for the vault

Returns: Promise<boolean> whether or not the secure storage mode is enabled


lockOut#

lockOut(): Promise<void>

Lock the user out without clearing their secure session information from the vault

Returns: Promise<void>


login#

login(session: T, authMode?: AuthMode): Promise<void>

Login a new session for the user. This method will clear the vault & any stored PIN for previously stored sessions.

Parameters:

NameTypeDescription
sessionTthe session to store
Optional authModeAuthMode

Returns: Promise<void>


logout#

logout(): Promise<void>

Log the user out entirely, and forget any stored authentication tokens

Returns: Promise<void>


onConfigChange#

onConfigChange(state: VaultConfig): any

Called when there has been a configuration change in the vault

Parameters:

NameType
stateVaultConfig

Returns: any


onPasscodeRequest#

onPasscodeRequest(isPasscodeSetRequest: boolean): Promise<string | void>

Called when attempting passcode unlock to allow for user defined passcode prompts.

Parameters:

NameTypeDescription
isPasscodeSetRequestbooleanWhether or not this is a request to set the passcode.

Returns: Promise<string | void>

  • a string to use as the passcode of undefined to use native prompts

onSessionRestored#

onSessionRestored(session: T): any

Called when the session object is restored.

Parameters:

NameTypeDescription
sessionTThe DefaultSession or user defined session that occurred.

Returns: any


onSetupError#

onSetupError(error: VaultError): any

Called when there is an error during vault setup

Parameters:

NameTypeDescription
errorVaultErrorThe VaultError that occurred.

Returns: any


onVaultLocked#

onVaultLocked(event: LockEvent): any

Called when the vault has been locked

Parameters:

NameTypeDescription
eventLockEventThe data about the lock event LockEvent

Returns: any


onVaultReady#

onVaultReady(state: VaultConfig): any

Called when the vault is ready

Parameters:

NameType
stateVaultConfig

Returns: any

  • A promise that resolves when the vault is successfully configured and available.

onVaultUnlocked#

onVaultUnlocked(state: VaultConfig): any

Called when the vault has been unlocked

Parameters:

NameType
stateVaultConfig

Returns: any


ready#

ready(): Promise<void>

Promise ensuring the user vault is ready to be accessed or denoting an error in setup;

Returns: Promise<void>

  • A promise that resolves when the vault is succesfully configured and available.

restoreSession#

restoreSession(): Promise<T | undefined>

Restore the session from the vault

Returns: Promise<T | undefined>


saveSession#

saveSession(session: T): Promise<void>

Store the session to the vault

Parameters:

NameTypeDescription
sessionTthe session to store

Returns: Promise<void>


setAuthMode#

setAuthMode(authMode: AuthMode): Promise<void>

Set the AuthMode for the vault. The vault must be unlocked or this will throw an error.

throws: VaultError - If the vault is locked or the mode is unavailale due to device hardware

Parameters:

NameTypeDescription
authModeAuthModeThe AuthMode to use.

Returns: Promise<void>


setBiometricsEnabled#

setBiometricsEnabled(isBiometricsEnabled: boolean): Promise<void>

Enable/Disable Biometric authentication

throws: VaultError - if biometrics is unavailable or the vault is locked

Parameters:

NameTypeDescription
isBiometricsEnabledbooleanwhether or not biometrics should be enabled

Returns: Promise<void>


setPasscode#

setPasscode(): Promise<void>

Set or change the passcode for the user This will call the onPasscodeRequest handler to allow for user defined passcode prompt. You can get more fine grain contol using the IdentityVault directly by calling getVault

throws: VaultError - if the vault is locked, passcode is disabled, user canceled pin prompt, or pin was mismatched

Returns: Promise<void>


setPasscodeEnabled#

setPasscodeEnabled(isPasscodeEnabled: boolean): Promise<void>

Enable/Disable passcode authentication. This will cause setPasscode to fire if passcode setup is required causing the onPasscodeRequest handler to fire to allow for user defined passcode prompt. You can get more fine grain contol using the IdentityVault directly by calling getVault

throws: VaultError - if the vault is locked

Parameters:

NameTypeDescription
isPasscodeEnabledbooleanwhether or not passcode should be enabled

Returns: Promise<void>


unlock#

unlock(authMode?: AuthMode): Promise<void>

Unlock the user's vault using the AuthMode configured for the vault or the override passed in to the call. This will call the onPasscodeRequest handler if the specified AuthMode allows for it to allow for user defined passcode prompt You can get more fine grain contol using the IdentityVault directly by calling getVault

Parameters:

NameType
Optional authModeAuthMode

Returns: Promise<void>



IonicNativeAuthPlugin#

IonicNativeAuthPlugin:

The native plugin

getVault#

getVault(config: PluginOptions): IdentityVault

Parameters:

NameType
configPluginOptions

Returns: IdentityVault



LockEvent#

LockEvent:

The lock event passed to the onVaultLocked handler.

saved#

● saved: boolean

If the data was persisted to the device before lock


timeout#

● timeout: boolean

If the lock was due to a background timeout



PluginConfiguration#

PluginConfiguration:

The configuration returned from IonicNativeAuthPlugin when getConfig is called.

descriptor#

● descriptor: VaultDescriptor

The values the uniquely identify the vault


hideScreenOnBackground#

● hideScreenOnBackground: boolean

Obscures the app when backgrounded to avoid leaking sensitive information, such as financial statements or balances


isBiometricsEnabled#

● isBiometricsEnabled: boolean

Whether biometric authentication is enabled for the vault


isPasscodeEnabled#

● isPasscodeEnabled: boolean

Whether passcode authentication is enabled for the vault


isPasscodeSetupNeeded#

● isPasscodeSetupNeeded: boolean

Whether a passcode needs to be set with setPasscode


isSecureStorageModeEnabled#

● isSecureStorageModeEnabled: boolean

Whether AuthMode.SecureStorage is enabled for the vault


lockAfter#

● lockAfter: number

The amount of number of milliseconds the app can be in the background for until the vault locks



PluginOptions#

PluginOptions:

The options passed the the IonicNativeAuthPlugin when creating a vault with getVault

<Optional> hideScreenOnBackground#

● hideScreenOnBackground: boolean

Obscures the app when backgrounded to avoid leaking sensitive information, such as financial statements or balances


<Optional> lockAfter#

● lockAfter: number

The amount of number of milliseconds the app can be in the background for until the vault locks


username#

● username: string

The username for the vault you wish to access


vaultId#

● vaultId: string

The vaultId for the vault you wish to access


<Optional> onConfig#

onConfig(event: PluginConfiguration): any

A handler that will receive events any time the vault is configuration is changed

Parameters:

NameType
eventPluginConfiguration

Returns: any


<Optional> onError#

onError(error: VaultError): any

Called when there is an error during vault setup

Parameters:

NameTypeDescription
errorVaultErrorThe VaultError that occurred.

Returns: any


<Optional> onLock#

onLock(event: LockEvent): any

A handler that will receive events any time the vault is locked

Parameters:

NameType
eventLockEvent

Returns: any


<Optional> onReady#

onReady(vault: IdentityVault): any

Called when the vault is configured and available.

Parameters:

NameTypeDescription
vaultIdentityVaultThe IdentityVault instance.

Returns: any


<Optional> onUnlock#

onUnlock(event: PluginConfiguration): any

A handler that will receive events any time the vault is unlocked

Parameters:

NameType
eventPluginConfiguration

Returns: any



VaultConfig#

VaultConfig:

The configuration file returned to event handlers such as onConfigChange and onVaultReady.

<Optional> authMode#

● authMode: AuthMode

The AuthMode to configure a new vault with. Note: This will only affect newly created vaults. Vaults with existing data and configuration will use there previous configuration. They can be change by unlocking and then chaning the AuthMode.

default: * BiometricAndPasscode


<Optional> hideScreenOnBackground#

● hideScreenOnBackground: boolean

Obscures the app when backgrounded to avoid leaking sensitive information, such as financial statements or balances

default: false


isPasscodeSetupNeeded#

● isPasscodeSetupNeeded: boolean

Whether a passcode needs to be set with setPasscode


<Optional> lockAfter#

● lockAfter: number

The amount of number of milliseconds the app can be in the background for until the vault locks. A value of 0 means the vault won't lock in the background.

default: 0



VaultDescriptor#

VaultDescriptor:

An interface that describes the vault. In IdentityVaultUser this defaults to _lastUser & default you can optionally add this to the constructor to accomplish advanced use cases multi-tenant vaults.

username#

● username: string

The username for the vault you wish to access


vaultId#

● vaultId: string

The vaultId for the vault you wish to access



VaultError#

VaultError:

An error that can be thrown by the plugin.

usage:

try {vault.unlock();} catch(e) { switch (e.code) {   case VaultErrorCodes.AuthFailed:     alert('You failed to authenticate!');     break;   case VaultErrorCodes.UserCanceledInteraction:     alert('You cancelled the face id prompt!');     break;   default:     throw e; }}

code#

● code: VaultErrorCodes


message#

● message: string



VaultOptions#

VaultOptions:

The options passed in to initialize the vault.

<Optional> authMode#

● authMode: AuthMode

The AuthMode to configure a new vault with. Note: This will only affect newly created vaults. Vaults with existing data and configuration will use there previous configuration. They can be change by unlocking and then chaning the AuthMode.

default: * BiometricAndPasscode


<Optional> hideScreenOnBackground#

● hideScreenOnBackground: boolean

Obscures the app when backgrounded to avoid leaking sensitive information, such as financial statements or balances

default: false


<Optional> lockAfter#

● lockAfter: number

The amount of number of milliseconds the app can be in the background for until the vault locks. A value of 0 means the vault won't lock in the background.

default: 0


<Optional> restoreSessionOnReady#

● restoreSessionOnReady: boolean

Whether or not to attempt to automatically restore the session when the vault is ready If restoreSessionOnReady and unlockOnAccess are both true the vault will be immediately unlocked & the session restored if onReady if the vault is in use.

default: false


<Optional> unlockOnAccess#

● unlockOnAccess: boolean

Whether or not to attempt to automatically unlock the vault when a value is accessed. If restoreSessionOnReady and unlockOnAccess are both true the vault will be immediately unlocked & the session restored if onReady if the vault is in use.

default: false


<Optional> unlockOnReady#

● unlockOnReady: boolean

Whether or not to attempt to automatically unlock the vault when the vault is ready

default: false



Type aliases#

BiometricType#

Ƭ BiometricType: "touchID" | "faceID" | "none"

The possible values returned by getBiometricType


Change Log#

[3.4.8] (2019-11-08)#

Bug Fixes#

  • vault-user: use the vault user methods to set the auth mode

[3.4.7] (2019-09-09)#

Bug Fixes#

  • Android: Fix an issue where the vault would not be cleared when fingerprints were added or all fingerprints were removed on Android..

[3.4.6] (2019-08-07)#

Bug Fixes#

  • Android: fix an issue where adding a fingerprint to device after the app was open would not refresh whether biometrics was available or not

[3.4.5] (2019-07-27)#

Bug Fixes#

  • Android, iOS: getSession return type and default IonicIdentityVaultUser generic to DefaultSession

[3.4.4] (2019-07-25)#

Bug Fixes#

  • Android: Fixes an issue on Android where getBiometricType would return none if Biometrics was not enabled even though the device had biometric hardware.

[3.4.3] (2019-06-14)#

Bug Fixes#

  • Android: Fixed issue where when hideScreenInBackground feature was enabled screenshots would be disabled.

[3.4.2] (2019-06-14)#

Bug Fixes#

  • iOS: Fixed an issue where the hide screen in background functionality was broken

[3.4.1] (2019-06-06)#

Bug Fixes#

  • Android: fix issue where setBiometricsEnabled(false) would throw an error if biometrics was unavailable

[3.4.0] (2019-06-06)#

Bug Fixes#

  • iOS: fix an issue where if a user removed fingerprints after authentication storing the session would return an error rather than default to passcode only mode
  • iOS: Fix issue where getBiometricType would return none if TouchID or FaceID was present on device but the user was not enrolled.
  • iOS: fix issue with getBiometricType and issue where lock event was triggered when lock was called in secure storage mode

Features#

  • Added android side of Secure Storage Mode
  • update Typescript/JS layer to support Secure Storage mode

[3.3.0] (2019-05-10)#

Bug Fixes#

  • Android, iOS: make the setting of the auth mode fault tolerant

Features#

  • Android. iOS: add Biometric or Passcode mode

[3.2.3] (2019-04-29)#

Bug Fixes#

  • Android: fix bug in Android where FingerprintManager import was missing

[3.2.2] (2019-04-29)#

Bug Fixes#

  • fix release configuration issue where xlmns:android was incorrectly add to manifest

[3.2.1] (2019-04-27)#

Bug Fixes#

  • fix bug where plugin id was incorrect and didn't include scope

[3.2.0] (2019-04-26)#

Features#

  • Added getPlugin method which can be overridden in advanced use cases to provide custom implementations for PWA compatibility etc.

Bug Fixes#

  • iOS: Fixed a bug on iOS where when using the hideScreenOnBackground flag the splashscreen may temporarily flash during biometric prompts.
  • Android: Fixed a bug on Android where isBiometricsAvailable would return true is some cases if No fingerprints were enrolled or fingerprint hardware wasn't available.
  • Android, iOS: Fixed a bug where getSession may incorrectly return undefined due to failing to wait for the plugin to be ready before returning.

[3.1.0] (2019-04-19)#

Features#

  • Added login method which clears the vault and stores the session passed to it.

[3.0.0] (2019-04-08)#

Features#