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>
  <!-- 0-1 occurrences (enabled if missing) - Whether the entire custom backend manager is enabled (if false, then no custom backend DLLs should be loaded) -->
  <Enabled type="bool" data="true"/>

  <!-- 0-n occurrences -->
  <Engine01>
    <!-- 0-1 occurrences (enabled if missing) - Whether this particular custom DLL is enabled (it must not be loaded if it is not enabled) -->
    <Enabled type="bool" data="true"/>

    <!-- 1-1 occurrences - Display-Name is completely arbitrary and is meant for display purposes in the config gui -->
    <Display-Name type="string" data="A special custom authentication DLL"/>

    <!-- 1-1 occurrences - The protocol ID string used to refer to this particular authenticator from within a policy -->
    <Protocol-Name type="string" data="MySpecialProtocol"/>

    <!-- 1-1 occurrences - The library path to the DLL that is the custom backend authenticator (the DLL is of course user defined) -->
    <Library-Path type="string" data="DummyEngine.dll"/>

    <!-- 0-1 occurrences - This is a special XML element that allows for user defined configuration data -->
    <Plugin-Config>
      <!-- 0-n occurrences (must be of type string) - Any string type entries in here are completely arbitrary. -->
      <My-Custom-Bit-Of-Data type="string" data="Hello world!"/>
    </Plugin-Config>
  </Engine01>
</Engines>