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

Modifying the Yes/No ASM

Prev Next

The Yes/No ASM can optionally be included in your app. It prompts the user to verify their presence by tapping a button on the device.

Adding Additional Localizations

The Yes/No ASM allows you to add additional localizations for its default UI. In order to add localizations, the application should add localizations for the following strings to its localizations:

String Resource ID

String Description

English Translation

nnl_asm_presence_description

Yes/No ASM description

You can set up the Yes/No ASM on your Android device to sign in to websites that use FIDO authentication. It's secure and more convenient than signing in with your username and password.

nnl_asm_presence_title

Yes/No ASM name

Presence

nnl_asm_presence_authorize

Title of default "Authorize" button

Authorize

nnl_asm_presence_decline

Title of default "Decline" button

Decline

nnl_asm_presence_register

Prompt text for registration operation

Do you want to authorize this registration?

nnl_asm_presence_login

Prompt text for authentication operation

Do you want to log in to your account?

The transaction text is retrieved from the message and should be localized on the Server.

Replacing the UI

The Yes/No ASM allows you to define a custom UI for its authorization screen. For a custom UI, the application should add a layout file named nnl_asm_presence_layout.xml. For the Yes/No ASM to function correctly, the custom layout must include the following elements:

Element type

Element ID

Description

TextView

asm_presence_text_view

A textview used for displaying the prompting text for the registration, authentication, and transaction operations.

Button

asm_presence_authorize_button

The "Authorize" button. The Yes/No ASM handles the button click and interprets it as an authorization for the current operation.

Button

asm_presence_decline_button

The "Decline" button. The Yes/No ASM will handle the button click and interpret it as a denial for the current operation.

The "Authorization" and "Decline" buttons can have custom text or can use the string resource IDs discussed in the previous section to use default/customized strings.