Certificate
This authenticator expects a configured HTTP header containing a X509 Certificate formatted as PEM.
Configuration
Section titled “Configuration”Common Authenticator configuration can be found here.
| Name | Description | Default value | Mandatory |
|---|---|---|---|
certificate_header_name | Name of the headers containing the certificate. | N/A | true |
missing_certificate_location | If the header contains no datat, where to redirect the client. | N/A | true |
custom_identifier | When logging events, the custom_identifier lets you tag the event. | N/A | false |
{ "id": "cert", "type": "CertificateAuth", "config": { "base_path": "/saml/authn", "certificate_header_name": "pemdata", "missing_certificate_location":"https://<custom_location>" }}Logging
Section titled “Logging”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)
Data exposed to global state
Section titled “Data exposed to global state”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 user interface and therefore exposes no Web Authenticator API. It reads the certificate from the request headers and completes without any dialogue with the browser.