The MobileAuthenticationClient interface represents the entry point to the SDK. Your application should generally create an application scoped MobileAuthenticationClient instance, by passing in a Configuration to the MobileAuthenticationClientInitializer that specifies the MobileAuthenticationClient behavior. The configuration defines the URLs used to perform operations with a NEVIS Mobile Authentication backend.

To create the MobileAuthenticationClient, assuming that the Configuration has already been created, here is an example using MobileAuthenticationClientInitializer to setup the SDK during application startup:

  async function createMobileAuthenticationClient(
configuration: Configuration
): Promise<void> {
await new MobileAuthenticationClientInitializer()
.onSuccess(client) => {
// handle the MobileAuthenticationClient
.onError((_error) => {
// handle error


  • MobileAuthenticationClient



operations: Operations

The object that can be used to invoke operations against the server.

localData: LocalData

The object that can be used to get information about the data (authenticators, device information) managed by the SDK.

Generated using TypeDoc