Safeguard Documentation Center
SSO AuthenticationSAML 2.0

CyberArk Identity

Configure CyberArk Identity as a SAML 2.0 identity provider for Safeguard.

CyberArk Identity

Example values

The tenant-specific values (the sg_ab12cde parts) show the shape only — Safeguard displays your real ACS URL and SP Entity ID in the Add Provider dialog after you click Save. This table makes it unambiguous which value goes on which side.

In CyberArk Identity — the SAML app / Trust details (you enter these at the IdP):

FieldExample value
Assertion Consumer Service URLhttps://api.safeguard.sh/auth/idp/realms/sg_ab12cde/broker/cyberark/endpoint
SP Entity IDhttps://api.safeguard.sh/auth/idp/realms/sg_ab12cde
NameID FormatEmail Address
email attributeattribute mapped to LoginUser.email

In Safeguard — Add Provider → SAML 2.0 (you copy these from the IdP):

FieldExample value
Aliascyberark
Display NameSign in with CyberArk Identity
SSO Service URLhttps://<tenant>.id.cyberark.cloud/saml2/idp/sso
Entity IDhttps://<tenant>.id.cyberark.cloud/<app-id>
X.509 Certificatethe PEM block below
-----BEGIN CERTIFICATE-----
MIIDdDCCAlygAwIBAgIGAX...(full cert from your IdP)...P3B/k0SolrFYPo
-----END CERTIFICATE-----
  1. In the CyberArk Identity Admin Portal, go to Apps & Widgets → Web Apps → Add Web Apps → Custom → SAML.
  2. Under Trust, set SP Entity ID to the SP Entity ID Safeguard shows after Save, and Assertion Consumer Service URL to the ACS URL Safeguard shows after Save.
  3. Set NameID Format to Email Address, with the NameID value resolving to the user's email.
  4. Under SAML Response → Attributes, add an attribute named email resolving to the user's email — separate from the NameID Format/value setting above.
  5. Copy the IdP Issuer URL and SSO endpoint, and download the IdP Certificate, from the app's Trust tab.
  6. In Safeguard, click Add Provider → SAML 2.0 → CyberArk Identity, and enter those three values.
  7. Assign the application to the appropriate Roles under the app's Permissions tab.
  8. Click Test in Safeguard to confirm.

Common errors: sign-in looping back to CyberArk usually means the NameID value variable is misconfigured (it must resolve to an actual email, not a bare username).

On this page