您位於此處:
OAuth 2.0 權杖交換流程
當 Salesforce 只是一個包含集中身分提供者及多個應用程式和微型服務的結構元件時,請使用 OAuth 2.0 權杖交換流程來簡化您的整合模式。透過此流程,將外部身分提供者的權杖交換為 Salesforce 權杖,並授與 Salesforce 資料的存取權。
當 Salesforce 只是一個包含集中身分提供者及多個應用程式和微型服務的結構元件時,請使用 OAuth 2.0 權杖交換流程來簡化您的整合模式。透過此流程,將外部身分提供者的權杖交換為 Salesforce 權杖,並授與 Salesforce 資料的存取權。
| 提供版本:Enterprise、Performance、Unlimited 及 Developer Edition |
若要深入瞭解此流程的運作方式與設定方式,請參閱這些資源。
Oauth2TokenExchangeHandler 抽象類別的 Apex 類別和權杖交換處理常式定義。若要開始使用,請建立 Apex 類別以在處理常式定義中參照。
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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.