Corsha Enterprise

Corsha Enterprise is a distribution of Corsha where all core components needed to run the complete Corsha mIDP are made available for installation into your enterprise environment, whether that is on-prem or in your cloud. With a Corsha Enterprise deployment, no external connections to the internet are require for the operation of Corsha's API MFA solution.

Architecture

The Corsha mIDP is functionally separated into two major component groups: The 'Customer Corsha Components' group and the 'Corsha Enterprise Components' group. The Customer Corsha Components group includes Authenticators and Gatekeepers (or Corsha integrations with other proxies and gateways). The Customer components are the same for both Corsha Cloud distributions and Corsha Enterprise distributions. The Corsha Enterprise Components group contains the Corsha authentication layer, administrative components, as well as the Distributed Ledger Network. The illustration below provides a simplified communication path diagram and shows the delineation between the component groups.

The 'Orderer' and 'Peer' components are part of Hyperledger Fabric, a free open-source project that serves as the Distributed Ledger Network (DLN) used to verify MFA credentials. The 'Root CA' and 'Inter CA' are the root Certificate Authority (CA) and intermediate CA's that provide the x509 certificates for both mutualTLS encryption of HTTPS traffic and signing keys for participants in the DLN. These CAs are implemented by Cert Manager resources in the Corsha Enterprise cluster.

There are also several Corsha microservices deployed to the Corsha Enterprise Cluster. These are represented in the diagram as the 'Authentication Service'. These services handle certain interactions with both clients and servers to manage MFA and to also provide monitoring and administrative capabilities, effectively acting like a Customer Control Plane for each customer to the DLN.

Requirements

Corsha Enterprise requires the use of Kubernetes 1.32+ to orchestrate the components of the DLN and other components. Corsha requires the use of DNS names to address its services and use SSL. We highly recommend you use a dedicated domain name for the Corsha Enterprise Components. If deploying to GKE, the gcloud CLI binary is required to be installed and configured.

Getting Started

To begin with your Corsha Enterprise deployment, follow the installation guide at Corsha Enterprise Installation