--- title: "SAML provider settings" slug: "saml-provider-settings-v7-0" description: "Configure SAML settings easily by uploading XML metadata, ensuring accurate Single Sign-On URL, Issuer, and Public Certificate for secure authentication." tags: ["SAML Provider", "IdP Configuration", "Identity Providers"] updated: 2026-06-05T19:17:40Z published: 2026-06-05T19:17:40Z canonical: "support.appgate.com/saml-provider-settings-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # SAML provider settings Complete the following fields in the **SAML Configuration** section of the **Add/Edit Identity Provider** page: - ***Use XML Metadata file.*** Upload the metadata XML file from your SAML provider to configure the provider. This populates the ***Single Sign-On URL***, ***Issuer***, and ***Public Certificate*** fields. This is the recommended way to populate these fields because it eliminates the need to match values between the SAML provider and AppGate ZTNA. Most SAML providers let you download metadata from their UI, or provide a dedicated URL for metadata. After you upload metadata, complete only ***Audience*** (and, optionally, ***Decryption Key***). To configure the provider manually, complete the following fields: - ***Audience.*** Audience URI. This value must exactly match the value in your SAML IdP settings under `.Assertion.Conditions.AudienceRestrictions[0].Audiences[0].AudienceURI`. - ***ForceAuthn.*** Enables the `ForceAuthn` flag in the SAML request. If your SAML provider supports this flag, users must enter credentials each time the client requires SAML authentication. - ***Public Certificate.*** The X.509 public key certificate that you download from your IdP. AppGate ZTNA uses it to verify that the SAML assertion is signed by the provider. The certificate must be used to create either the assertion signature in `Response > Assertion > Signature > SignatureValue` or the token signature in `Response > Signature > SignatureValue`. Paste the certificate contents into the dialog box, or click **Choose a file** and browse to the file. > [!NOTE] > **NOTE** > > When certificates approach expiration, the Controller shows a dashboard warning 30 days in advance. - ***Decryption Key.*** Optional. Private PEM key used to decrypt encrypted assertions