IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 11 of 30

Universal Containers (UC) is using a custom application that will act as the Identity Provider and will generate SAML assertions used to log in to…

Full set: 248 questions
Universal Containers (UC) is using a custom application that will act as the Identity Provider and will generate SAML assertions used to log in to Salesforce. UC is considering including custom parameters in the SAML assertion. These attributes contain sensitive data and are needed to authenticate the users. The assertions are submitted to salesforce via a browser form post. The majority of the users will only be able to access Salesforce via UC's corporate network, but a subset of admins and executives would be allowed access from outside the corporate network on their mobile devices. Which two methods should an Architect consider to ensure that the sensitive data cannot be tampered with, nor accessible to anyone while in transit?
Answer options
A: Use the Identity Provider's certificate to digitally sign and Salesforce's Certificate to encrypt the payload. Correct answer
B: Use Salesforce's Certificate to digitally sign the SAML Assertion and a Mobile Device Management client on the users' mobile devices.
C: Use the Identity provider's certificate to digitally Sign and the Identity provider's certificate to encrypt the payload.
D: Use a custom login flow to retrieve sensitive data using an Apex callout without including the attributes in the assertion. Correct answer
Correct Answer:
A. Use the Identity Provider's certificate to digitally sign and Salesforce's Certificate to encrypt the payload.; D. Use a custom login flow to retrieve sensitive data using an Apex callout without including the attributes in the assertion.
Explanation

To protect sensitive data in a SAML assertion, two primary security goals must be met: integrity and confidentiality.
1. Integrity and Authenticity: The assertion must be digitally signed by the Identity Provider (IdP) using its private key. The Service Provider (Salesforce) then verifies this signature using the IdP's public key (certificate). This ensures the assertion has not been tampered with and originates from the trusted IdP.
2. Confidentiality: The assertion, or its sensitive attributes, must be encrypted. The IdP encrypts the payload using the SP's (Salesforce's) public key. Only Salesforce, holding the corresponding private key, can decrypt it. Option A correctly describes this standard SAML security mechanism.
Option D presents an alternative, highly secure architectural pattern. It avoids sending sensitive data through the user's browser (front-channel) entirely. Instead, a Salesforce Login Flow triggers a server-to-server (back-channel) Apex callout to securely retrieve the data after the user is authenticated. This eliminates the risk of browser-based interception.

Why Incorrect

B. The Service Provider (Salesforce) does not sign the SAML assertion; this is the responsibility of the Identity Provider to prove the assertion's origin and integrity.
C. Encryption for confidentiality requires using the recipient's (Salesforce's) public key. Encrypting with the Identity Provider's own certificate would mean only the IdP could decrypt it, making it useless to Salesforce.

References

1. OASIS Security Assertion Markup Language (SAML) V2.0 Core Specification:

For Signing (Integrity): Section 2.3.1

"Element

" states

"Assertions are signed by the asserting party

to protect the integrity of the assertion and to authenticate the issuer." The asserting party is the Identity Provider.

For Encryption (Confidentiality): Section 5.3.1

"Encryption

" specifies that the key used for encryption is typically the public key of the relying party (the Service Provider

which is Salesforce in this case). This directly supports option A and refutes option C. (Document identifier: oasis-sstc-saml-core-2.0-os).

2. Salesforce Help & Training

Single Sign-On Implementation Guide:

For Encryption: The section "Enable Encrypted SAML Assertions" explains that Salesforce uses an uploaded certificate (containing a public key and its corresponding private key) to decrypt assertions. This implies the IdP must use Salesforce's public key to encrypt

validating option A.

3. Salesforce Help & Training

Login Flows:

The documentation on "Login Flow Use Cases" and "Login Flow Examples" demonstrates that a login flow can invoke an Apex class. This Apex class can then make a secure

server-to-server callout to an external service to retrieve or validate user data post-authentication

which validates the architectural pattern described in option D.

Scroll to Top