General Custom Authenticators configuration
Custom Authenticators is an optional component of the Token Server. If you want to use it, first make sure docker-compose
property TOKEN_SERVER_COMMON_FEATURES_EXPERIMENTAL_FEATURES_ENABLED_BOOLEAN
is set to true
.
To perform Custom Authenticators operations, Token Service makes calls to Extension Engine Service.
To configure Token Server and Extension Engine communication, following properties are required to set in docker-compose
file:
TOKEN_SERVER_COMMON_EXPERIMENTAL_EXTENSION_ENGINE_BASIC_AUTHENTICATION_USERNAME
TOKEN_SERVER_COMMON_EXPERIMENTAL_EXTENSION_ENGINE_BASIC_AUTHENTICATION_PASSWORD
TOKEN_SERVER_COMMON_EXPERIMENTAL_EXTENSION_ENGINE_URL
Application configuration
Custom authenticators can be enabled per Application in the Token Server.
Go to Configuration
→ App configuration
→ Applications
and add or edit an Application.
Field | Required | Example value | Details |
---|---|---|---|
Custom Authenticators enabled | No | Enables / disables Custom Authenticators for the application |
Mobile authentication
To use mobile authentication via a custom authenticator. Configure a mobile authentication type like it is done for any other type. See the topic guide for
mobile authentication. Select
PUSH_WITH_CUSTOM_AUTHENTICATOR
as authentication method and fill out all other required fields.