Hyland Identity and Access Management (IAM) services uses the Hyland Identity Provider (IdP) server to authenticate connections to supported applications, such as OnBase.
Complete configuration requires that the OnBase application is configured to use the Hyland IdP server for authentication, and also that a client connection is configured for each application on the Hyland IdP server.
This chapter describes how to integrate the various OnBase clients and modules with the Hyland IdP server. See:
-
Configuring the Client and Configuration Modules to Use IdP Authentication
-
Configuring the Application Server to Use IdP Authentication
-
Configuring the Web Server and Web Client to Use IdP Authentication
Complete details on configuring the Hyland IdP server are documented in the separate Identity and Access Management Services documentation. Version compatibility with OnBase Foundation releases is documented in the Version section of that documentation.
An identity provider environment can also be configured to use a third-party authentication provider, allowing for federated authentication. The third-party authentication provider adds an additional layer of authentication and communication with the user agent on the client workstation. See Configuring Third-Party Authentication Providers.
Detailed instructions on how to configure a third-party authentication provider to correctly authenticate and return valid tokens for use with the Hyland IdP server are beyond the scope of this documentation. Where possible we have provided generalized instructions using SAML terminology, but detailed instructions should be available from the specific third-party provider being used.