Mobile Authenticator Studio actions

Once the user has activated an account of the authenticator, action buttons are displayed in the main screen of the app to provide access to each cryptographic application.

The following elements must be set in the app’s configuration file to define an action:

Index of the cryptographic application

(Optional) This index determines the cryptographic application that will be used to generate authenticator responses. For example, an action can simply be configured to open a URL.

QR code or Cronto image input

An image scanner is launched to scan a QR code or Cronto image that contains the data. The content for a Cronto image comes by default in the required format. The content of the QR code for signing data fields must have the following format:

<QRCode>
<DTF1> DATA_TO_SIGN_1 </DTF1>
<DTF2> DATA_TO_SIGN_2 </DTF2>
<DTF3> DATA_TO_SIGN_3 </DTF3>
<DTF4> DATA_TO_SIGN_4 </DTF4>
<DTF5> DATA_TO_SIGN_5 </DTF5>
<DTF6> DATA_TO_SIGN_6 </DTF6>
<DTF7> DATA_TO_SIGN_7 </DTF7>
<DTF8> DATA_TO_SIGN_8 </DTF8>
</QRCode>

The QR code or Cronto image for the challenge input contains the challenge value only, without additional formatting:

123456

Once scanned, the action can be configured to display the data extracted from the QR code or Cronto image for review by the user. The fields are read-only.

.Each action can be configured to support data field input through an image. Contextual signing is applied, which means that the data fields to sign are provided from different sources, according to the context in which the authenticator action is used.