Set Up an External Identity Provider to Encrypt SAML Assertions
When you configure Salesforce as the service provider in a SAML single sign-on (SSO)
configuration, you can pick a saved certificate to decrypt inbound assertions from external
identity providers. These instructions show you how to edit your SSO configuration so that your
external identity provider can encrypt SAML assertions.
Required Editions
Available in: both Salesforce Classic and Lightning Experience
Federated Authentication is available in: All
Editions
Delegated Authentication is available in:
Professional, Enterprise, Performance,
Unlimited, Developer, and Database.com
Editions
Authentication Providers are available in:
Professional, Enterprise, Performance,
Unlimited, and Developer Editions
From Setup, in the Quick Find box, enter Single, and then select
Single Sign-On Settings.
Next to your SSO configuration, click Edit.
For Assertion Decryption Certificate, select the certificate that you want to use for
encryption.
Verify that your SAML Identity Location from your original configuration is accurate. If
not, select an option based on where your identity provider stores the user’s identifier,
meaning their Salesforce username or federationIdentifier, in SAML assertions.
If the user’s identifier is in the <Subject>
statement of the assertion, select Identity is in the NameIdentifier element of the
Subject statement.
If the user’s identifier is in an <AttributeValue> in the assertion’s <Attribute>, select Identity is in an Attribute
element.
If you selected Identity is in an Attribute element, fill out these
fields.
Attribute Name—Enter the value of the AttributeName parameter specified in the <Attribute> element in your identity provider’s SAML assertions. This value
matches the User ID.
Name ID Format—Enter the value of the nameid-format in your identity provider’s SAML assertions, such as unspecified, emailAddress,
or persistent. For a list of all possible values, see the
Name Identifier Format Identifiers section in the Assertions and Protocols SAML 2.0
specification.
Save the settings.
After you make these changes, the value for the Salesforce Login URL changes in your
SAML configuration.
Copy your new Salesforce Login URL value.
Share the new Salesforce Login URL with your identity provider.
To help your identity provider encrypt assertions, share a copy of the certificate in the
Assertion Decryption Certificate field.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.