Skip to content

Fortified IDDocs

Chain

Configuration and usage guidance for Chain in Fortified ID Access.

The chain authenticator orchestrates one or more authenticators that perform(s) the actual authentication.

The chain is complete when all (required) authenticators in the chain are completed.

A chain authenticator can be nested with Selectors and other chains.

Common Authenticator configuration can be found here.

Name Description Default
base_path The base path for this authenticator and used to construct paths for chained authenticators. (see Routing)
exec_if An expression that determines if this authenticator should be executed or not.
chain List of authenticator refs defining the content and order of the chain. An empty chain will block the authentication and therefore at least one ref must be present. []
require_subject Flag controlling if this authenticator requires a subject to be set before completing. Use only for nested chains. true
proceed_on_error Flag controlling how chain behaves on authenticator failure. If enabled, all authenticators in chain will be executed before error is raised (stealth behaviour). true
require_chain Flag specifying if this authenticator must be executed inside a chain. false
verbose Turns on extended trace logging. Use for troubleshooting only. false

An authenticator ref points to an actual authenticator available in the current configuration.

NameDescriptionDefaultMandatory
idAuthenticator idtrue
requiredFlag controlling if authenticator is required to complete or not. Authentication will fail if a required authenticator does not complete.truefalse
orderIf ALL items have order numbers, these numbers define the execution order. If NO item has an order number, the order of the list defines the execution order.false

When a chain is executed, the user agent is redirected to each chained authenticator in the specified (configured) order. The path to the authenticator is constructed by combining base_path with the chain authenticator's ID (specified as id in authenticator_ref).

Note that base_path is also used to generate the path for the current authenticator. This is intentional, as all authenticators in a flow must share the same path and session, both of which are managed by the path.

API not available.