Skip to content

Fortified IDDocs

With QR or "app-switch"

This authenticator expects users either scan a QR code or "app-switch".

This is the configuration for the TaskViewAuthenticator

Common Authenticator configuration can be found here.

NameDescriptionDefault valueMandatory
internal_http_destinationID of the internal http client used to talk with backend."default"false
username_parameterParameter to where the username is exported."username"false
server_api_urlAddress to the mobile server api module.N/Atrue
timeout_secondsTime to live before the authenticator expires
(0 is forever)
0false
task_formThe task-form to be used in the authentication.N/Atrue
webroot_dirSee common authenticator configurationweb/mobileid/taskviewauthenticatorfalse

Apart from system logging, event logging is done when starting, completing, and failing a transaction.

Event ids are:

  • MOBILE_ID_100101("MobileID authentication started")
    • IDENTIFIER (session trace id)
  • MOBILE_ID_100102("MobileID authentication completed")
    • IDENTIFIER (session trace id)
    • SOURCE_USER_NAME (user subject)
  • MOBILE_ID_100103("MobileID authentication rejected")
    • IDENTIFIER (session trace id)
  • MOBILE_ID_100104("MobileID authentication canceled")
    • IDENTIFIER (session trace id)
  • MOBILE_ID_100105("MobileID authentication expired")
    • IDENTIFIER (session trace id)

After a user completes a transaction, the authenticator is marked as done. Data from the authentication response is then put into the global state, replacing existing values:

  • "username_parameter" set to user subject