Explore scenarios for configuring named credentials to make callouts to various external
systems. The examples cover the entire named credential configuration for different
authentication protocols and principal types.
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
Available in: all editions
Named Credential Example: OAuth 2.0 Browser Flow with a Named Principal In this example, configure a named credential with the OAuth 2.0 Browser Flow to make authenticated callouts to GitHub. This example uses the Named Principal identity type, meaning that a Salesforce admin authenticates to GitHub on behalf of all users in the org.
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.
