Configuring a Custom Authenticator - Legacy Authentication Methods - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Legacy Authentication Methods

Legacy Authentication Methods
Foundation 23.1

A custom authenticator is the specific component that is invoked to retrieve the user's user name. Custom authenticators can be created to support customer requirements. Please contact your first line of support to create or integrate a custom single sign-on solution.

To configure a custom authenticator, the consuming application must have a .NET config file. If a .NET config file does not exist for the consuming application, then one must be created. For web applications, the .NET config file must be named web.config. For client applications, the .NET config file must be named the same name as the executable (e.g., DMDesktop.exe.config or wscript.exe.config).

The .NET config file must be configured with a specific configSection and Hyland Authentication elements. An example config file is included here:



<section name="Hyland.Authentication" type="Hyland.Authentication.Configuration.CustomAuthenticationConfigHandler, Hyland.Authentication, Version=, Culture=neutral, PublicKeyToken=c02e21dc39c53bb0" />


<Hyland.Authentication Type="Hyland.Authentication.NtAuthenticationProvider, Hyland.Authentication.NtAuthentication">


<add key="stripDomainFromUsername" value="true" />


</Hyland.Authentication >



Contact your first line of support for assistance with correctly updating the values of these elements to meet the needs of your custom single sign-on deployment.