What two authentication protocols are available when configuring an external data source for Salesforce Connect?

When configuring an external data source for Salesforce Connect, the process of authentication is crucial to ensure secure data access and integration. The correct answer, which states that Password authentication and OAuth 2.0 are available protocols, highlights two widely supported methods for authenticating users and applications.

Password authentication allows users to enter their credentials directly within the Salesforce platform, which can be straightforward for accessing external systems. This method is straightforward but requires a secure management approach to protect user passwords.

OAuth 2.0, on the other hand, is a more modern authentication framework that enables third-party applications to obtain limited access to user accounts without revealing passwords. It provides a more secure way to authorize access, especially for applications that need to access Salesforce and other services on behalf of a user. This token-based method enhances security by allowing users to grant access while retaining control over their credentials.

In contrast, the other options revolve around different forms of authentication that may not be specifically supported for Salesforce Connect external data sources. For example, JWT and Bearer Token authentication are often used in API contexts but do not apply directly to Salesforce Connect’s configuration. Similarly, Federated authentication and SAML are primarily used for single sign-on scenarios rather than for accessing external data sources directly within Salesforce Connect