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

What item should an Architect consider when designing a Delegated Authentication implementation?

Full set: 248 questions
Answer options
A: The Web service should be secured with TLS using Salesforce trusted certificates. Correct answer
B: The Web service should be able to accept one to four input method parameters.
C: The web service should use the Salesforce Federation ID to identify the user.
D: The Web service should implement a custom password decryption method.
Correct Answer:
A. The Web service should be secured with TLS using Salesforce trusted certificates.
Explanation

When implementing Delegated Authentication, Salesforce makes a synchronous web service callout to an external endpoint, sending the user's credentials for validation. This communication contains sensitive information (username and password) and must be protected from interception. Therefore, the external web service endpoint must be secured using Transport Layer Security (TLS). Salesforce servers must also be able to trust the certificate presented by the endpoint, meaning it must be issued by a Salesforce-trusted Certificate Authority. This ensures the confidentiality and integrity of the authentication request and response, which is a fundamental security requirement for the design.

Why Incorrect

B. The Web service should be able to accept one to four input method parameters. This is incorrect. The Delegated Authentication WSDL specifies a precise method signature, Authenticate(username, password, sourceIp), which requires exactly three input parameters.
C. The web service should use the Salesforce Federation ID to identify the user. This is incorrect. The callout sends the user's username for validation, not the Federation ID. The Federation ID is typically used as a unique identifier in SAML-based Single Sign-On (SSO) assertions.
D. The Web service should implement a custom password decryption method. This is incorrect. Salesforce sends the password in clear text over the secure TLS channel. The web service receives the password as entered by the user and does not need to perform any decryption.

References

1. Salesforce Help Documentation, "Set Up Delegated Authentication": This document explicitly states the security requirements. Under the "Enable Delegated Authentication" section, it notes, "The web service must be accessible to Salesforce servers using SSL encryption with a valid, trusted certificate." This directly supports answer A.

2. Salesforce Developer Documentation, "Single Sign-On Implementation Guide": In the chapter "Single Sign-On with Delegated Authentication," the guide provides the WSDL for the authentication web service. The WSDL defines the Authenticate operation with three specific input parameters: username, password, and sourceIp. This directly refutes option B and shows that username is used, refuting option C.

3. Salesforce Identity and Access Management Architecture, Official Courseware (IAM-450): Module on "Delegated Authentication" details the callout mechanism, emphasizing that the connection must be over HTTPS (which uses TLS/SSL) and that the password is sent as a string element within the SOAP request body, not as an encrypted value requiring custom decryption by the endpoint. This refutes option D.

Scroll to Top