Skip to content

Fortified IDDocs

Certificate

This authenticator expects a configured HTTP header containing a X509 Certificate formatted as PEM.

Common Authenticator configuration can be found here.

NameDescriptionDefault valueMandatory
certificate_header_nameName of the headers containing the certificate.N/Atrue
missing_certificate_locationIf the header contains no datat, where to redirect the client.N/Atrue
custom_identifierWhen logging events, the custom_identifier lets you tag the event.N/Afalse

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

Event ids are:

  • WEB_100013("Authentication using certificate completed")
    • IDENTIFIER (user trace id)
    • SOURCE_ADDRESS (ip address of device starting transaction)
    • CUSTOMER_IDENTIFIER (if configured)
    • SOURCE_USER_NAME (subject from the certificate)
    • MESSAGE (certificate serial)

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:

  • serial
  • subject
  • certificate

This authenticator has no UI