Integrate auto launch

Users can launch a Mobile Authenticator Studio app and execute a defined action by clicking on a URL that has the following format:

${scheme}://${actionName}

where:

• ${scheme} is a string specified when customizing the Mobile Authenticator Studio app, according to iOS and Android scheme policies.

• ${actionName} can be one of the following:

  • onlineactivationid

  • offlineactivationid

  • actionid

The action name can be followed by the action parameters in the following format:

$scheme://${actionName}?ActionParameterName1=ActionParameterName1Value&ActionParameterName2=ActionParameterName2Value

Action and parameter names are case-insensitive.

If the URL format is incorrect, the application will display an error message and terminate. Unknown parameters are silently ignored.

Online activation

When the digipass://MyOnlineActivationId URL is clicked, it launches the online activation with the identifier MyOnlineActivationId.

This action supports the following parameters:

• Identifier. This is the registration identifier. It is an alphanumeric string limited to 40 characters.

• AuthorizationCode. This is the authenticator authorization code. It is an alphanumeric string limited to 40 characters.

• ActivationPassword. This is the authenticator activation password. It is an alphanumeric string limited to 40 characters.

• UserID. This is the extra user identifier. This value can be modified once it is displayed for validation. It is an alphanumeric string limited to 40 characters.

All parameters are optional.

Offline activation

When the ${scheme}://offlineactivationid URL is clicked, it launches the offline activation for the Mobile Authenticator Studio app.

This action supports the following parameters:

• SerialNumber. This is the authenticator serial number. It is composed of 3 letters and 7 digits.

  Do not use a serial number suffix (e.g. “1280189”) instead of the full serial number (e.g. “FDM1280189”) in the activation URL. The serial number prefix will be retrieved from the static vector. Thus, the serial number prefix can differ from the static vector that is hardcoded in the mobile application (e.g. “FDL”) and the authenticator BLOB used by the server (e.g. “FDM”). In this case, the authenticator instance will be properly activated, but the generated authenticator responses (i.e. one-time password and signature) will be invalid.

• ActivationCode. This is the authenticator activation code. It is a hexadecimal character string.

• ERC. This is the authenticator event reactivation counter. This value can be modified once it is displayed for validation.

• UserID. This is an extra user identifier. This value can be modified once it is displayed for validation.

• challenge. This is the challenge used in case of post-activation with a challenge-based cryptographic application. This value can be modified once it is displayed for validation.

All parameters are optional.

Authenticator actions

When the digipass://MyActivationId URL is clicked, it launches the offline activation with the identifier MyActivationId.

This action supports the following parameters:

• SerialNumber. This is the authenticator serial number to use if the authenticator application is configured in the multi-instance mode.

• dtf1. This is the first data field to sign.

• dtf2. This is the second data field to sign.

• dtf3. This is the third data field to sign.

• dtf4. This is the fourth data field to sign.

• dtf5. This is the fifth data field to sign.

• dtf6. This is the sixth data field to sign.

• dtf7. This is the seventh data field to sign.

• dtf8. This is the eighth data field to sign.

• challenge. This is the challenge.

challenge and the dtfx parameters cannot be combined in the same URL.