The Common SAML Metadata feature enables administrators to configure Security Assertion Markup Language (SAML) authentication settings at the Customer Pod Architecture (CPA) level.
This functionality provides centralized control over SAML metadata distribution, certificate management, and entity identification across multiple pod deployments within your Omnissa environment.
Prerequisites
Before configuring Common SAML Metadata at the CPA level, ensure the following requirements are met:
- Administrator access to Horizon Console.
- Valid SAML encryption and signing certificates in PFX format to ensure that both public and private keys are included.
- Valid X.509 certificates for SAML encryption & signing.
Checklist for Multi-Pod Configuration
To achieve CPA-level common SAML metadata, complete the following for each pod:
- Upload SAML Encryption Certificate
- Upload SAML Signing Certificate
- Navigate to pod-specific Metadata Settings
- Configure Enable Key Sharing setting
- Configure Enable Entity ID Sharing setting
- Configure the shared Entity ID to a common value across all pods
For configuring Metadata Settings, see Configure a SAML Authenticator in Horizon Console
Certificate Management
Certificate Management is the foundation of SAML authentication configuration. Administrators must upload both encryption and signing certificates before configuring SAML metadata settings.
| Certificate Types | Description |
|---|---|
| SAML Encryption | Encrypts SAML assertions exchanged between the identity provider and service provider. |
| SAML Signing | Digitally signs SAML requests and responses to ensure integrity and authenticity. |
Note: The administrator must upload the same certificate across all pods for both encryption and signing before configuring the SAML metadata settings.
Was this page helpful?