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 section describes how to configure the following OnBase modules to use Hyland IdP authentication:
- Configuring Agenda to Use IdP Authentication
- Configuring Bar Code Generator to Use IdP Authentication
- Configuring DeficiencyPop to Use IdP Authentication
- Configuring Desktop Host to Use IdP Authentication
- Configuring Disconnected Scanning to Use IdP Authentication
- Configuring DocPop, FolderPop, FormPop, WorkflowPop, and PDFPop to Use IdP Authentication
- Configuring Document Composition to Use IdP Authentication
- Configuring Environment Value Management to Use IdP Authentication
- Configuring Express Scanning to Use IdP Authentication
- Configuring the External Access Client to Use IdP Authentication
- Configuring Front Office Scanning to Use IdP Authentication
- Configuring Governance Rules as a Service to Use IdP Authentication
- Configuring the Hyland Office Integrations to Use IdP Authentication
- Configuring Integration for Duck Creek to Use IdP Authentication
- Configuring the Medical Records Management (MRM) Client to Use IdP Authentication
- Configuring Patient Window to Use IdP Authentication
- Configuring REQConnect to Use IdP Authentication
- Configuring Studio to Use IdP Authentication
- Configuring Unity Client for Use with SAP ArchiveLink to Use IdP Authentication
- Configuring the Unity Management Console to Use IdP Authentication
For details on configuring the OnBase clients and servers to use Hyland IdP authentication, see: