Digipass S3 is now DigipassONE. This section is currently being updated to reflect our new name.

Exploring the Wear OS Tutorial App

Prev Next

What is the Wear OS Tutorial App?

The Wear OS Tutorial App is a sample application that runs on Wear OS devices. The following sections describe how to use the Wear OS Tutorial App and its operations.

How does Wear OS Tutorial App Work?

  • Compared to the standard Tutorial app, the Wear OS Tutorial App has limited functionality. It consists of two screens:

    • Sign In - supports login and authentication functionality

    • Actions screen - supports registration, deregistration and sign out functionality

  • For each operation, the Wear OS Tutorial App does the following:

    • Sends a request to the Server to receive a request for the selected operation

    • Processes the request by the App SDK and receives the response

    • If it succeeds locally, passes the response to the Server and validates the response

  • Wear OS Tutorial App includes the asm_watch_wear library which acts as a remote watch authenticator for an Android mobile application. Wear OS Tutorial App does the following:

    • Processes registration and authentication requests received from an Android mobile app.

    • Shows a UI to verify user presence for registration and authentication and also displays transaction confirmation.

    • Returns results to the mobile application

Building the Wear OS Tutorial App

The Wear OS version of Tutorial App can be built from the included Android Studio project source files. Sources are included in the same project using a separate flavor. You can install the app on physical devices or emulators running Wear 2.0 (Android Wear 7.1.1 API 25 and higher).

By default, the Tutorial App is set up to produce an Android app. To switch to the Wear OS version of Tutorial App, do the following:

  1. Open the Build Variants window on the left side of Android Studio.

  2. Switch Active build variant from androidDebug to wearosDebug.

  3. Perform gradle synchronization and build the application.

When the App SDK runs on Wear OS it only supports a silent authenticator. The silent authenticator stores the key in the keystore. Depending on the manufacturer, it could be software or hardware keys.

Running the Wear OS Tutorial App

The Wear OS Tutorial app consists of two screens, Sign In and Actions. The second screen is only shown after a user successfully signs in.

Sign In Screen

Use this screen to sign in to the Server, a prerequisite to registration. After successful registration, the same screen is used for passwordless authentication. The sign in screen is implemented as a fragment class called LoginFragment.

If this is your first time registering:

Enter a unique username of your choice, e.g. your email address.

A unique username avoids possible username collisions with other user accounts on the Digipass S3 evaluation server.

Enter "noknok" for the password, then tap Sign In.

Next is the Actions Screen where you can register an authenticator.

If you have already registered:

Since you have already registered authenticators, you can do passwordless sign in.

Enter your existing user name, then tap Sign In.

Actions Screen

This screen allows you to perform FIDO registration, deregistration, and logout. This screen is implemented using the ActionFragment class.

By tapping the Register button, you can register a new silent authenticator.

After successful registration, the authenticator is ready to use for passwordless authentication.

If the authenticator was already registered, the app displays a "No more authenticators available" error message.

Deregister deletes the current user's registered silent authenticator.

Sign Out signs you out and switches back to Sign In Screen where you can sign in again with a password or authenticate using FIDO if you have valid registration.

About the App SDK for Wear OS

The App SDK for Wear OS, which supports Quick Authentication, has the following limitations:

  • Only supports silent authentication

  • Only supports the UAF protocol

  • Does not allow account selection

  • Does not support Adaptive Authentication

  • Does not support out-of-band authentication