Custom Authentication Engine Definitions via the Configuration File

You can define an authentication engine for back-end authentication via the OneSpan Authentication Server configuration file, i.e. identikeyconfig.xml. By default, this file is located in:

• /etc/vasco/ias (Linux)
• %PROGRAMFILES%\VASCO\IDENTIKEY Authentication Server\bin (Windows)

The OneSpan Authentication Server configuration file contains all custom authentication engines within the Engines element. The following snippet shows a typical Engines section containing a custom engine entry. Such an entry would typically be nested in the BackEndAuthenticators element.

<Engines>
    <!-- Whether the entire custom backend manager is enabled (if false, then no custom backend DLLs should be loaded) -->
    <Enabled type="bool" data="true"/>
    <!-- Occurrences for each engine -->
    <Engine>
        <!-- Whether this particular custom DLL is enabled (it must not be loaded if it is not enabled) -->
        <Enabled type="bool" data="true"/>
        <!-- The display name for this engine -->
        <Display-Name type="string" data="A special custom authentication DLL"/>
        <!-- The protocol ID string used to refer to this particular authenticator from within a policy -->
        <Protocol-Name type="string" data="MySpecialProtocol"/>
        <!-- The library path to the DLL that is the custom backend authenticator (the DLL is user defined) -->
        <Library-Path type="string" data="DummyEngine.dll"/>
        <!-- User-defined configuration data -->
        <Plugin-Config>
            <!-- Any string type entries are completely arbitrary -->
            <My-Custom-Bit-Of-Data type="string" data="Hello world!"/>
        </Plugin-Config>
    </Engine>
</Engines>