About This Architecture

Compass Pilot implements a three-tier authentication architecture spanning Dev, QA, and Prod environments on OCI, with Microsoft Entra ID as a shared external SAML identity provider. Users authenticate through Compass Pilot ClickOnce clients to environment-specific Hyland Identity Services, which federate with the centralized Entra ID SAML IdP for credential validation. Each tier routes authenticated requests through Hyland API Servers to OnBase Server backends, ensuring consistent identity governance across development, testing, and production workloads. Fork this diagram on Diagrams.so to customize environment-specific configurations, add additional IdP providers, or document your own multi-tenant Hyland deployment. This pattern demonstrates least-privilege federation and environment isolation best practices for enterprise content management platforms.

People also ask

How do you implement federated SAML authentication across multiple Compass Pilot environments with Hyland and OnBase Server?

This diagram shows a three-tier architecture where Compass Pilot ClickOnce clients in Dev, QA, and Prod authenticate through environment-specific Hyland Identity Services that federate with a shared Microsoft Entra ID SAML provider. Each tier maintains isolated OnBase Server backends while sharing a single external identity provider, enabling consistent credential management and audit trails acros