Gebruik het eindpunt OpenID Connect Discovery om een query te maken voor informatie over de configuratie van Salesforce OpenID Connect. Salesforce retourneert basisgegevens over eindpunten, ondersteunde bereiken en andere waarden die voor OpenID Connect-autorisatie worden gebruikt.
| Beschikbaar in: zowel Salesforce Classic als Lightning Experience |
| Beschikbaar in: Alle editions |
Er is geen sessie vereist om toegang tot dit eindpunt te krijgen.
De indeling van de URL is https://MyDomainName.my.salesforce.com/.well-known/openid-configuration.
De URL's voor sandboxen en Experience Cloud-sites hebben een andere notatie.
De inlog-URL voor Mijn domein van uw organisatie voor een sandbox vindt u op de pagina Set-up van Mijn domein.
In het geval van een Experience Cloud-site die een geauthenticeerde LWR-site is die is gemaakt na Winter '23 heeft de URL-structuur de notatie MijnDomeinnaam.my.site.com/mycommunityurlvforcesite/.well-known/openid-configuration. Als u de waarde voor uw URL tot /openid-configuration wilt achterhalen, gaat u naar Set-up | Aangepaste URL's en zoekt u de volledige URL van de community met dezelfde naam als uw Experience Cloud-site.
Voor alle andere typen Experience Cloud-sites, wordt MijnDomeinnaam.my.salesforce.com vervangen door de URL van de site, zoals bivoorbeeld MijnDomeinnaam.my.site.com/mycommunityurl/.well-known/openid-configuration.
In alle scenario's moet de URL het HTTPS-protocol gebruiken.
Het OpenID Connect Discovery-eindpunt retourneert de gegevens in JSON-indeling.
{"issuer":"https://login.salesforce.com",
"authorization_endpoint":"https://login.salesforce.com/services/oauth2/authorize",
"token_endpoint":"https://login.salesforce.com/services/oauth2/token",
"revocation_endpoint":"https://login.salesforce.com/services/oauth2/revoke",
"userinfo_endpoint":"https://login.salesforce.com/services/oauth2/userinfo",
"jwks_uri":"https://login.salesforce.com/id/keys",
"registration_endpoint": "https://login.salesforce.com/services/oauth2/register",
"introspection_endpoint": "https://login.salesforce.com/services/oauth2/introspect",
"scopes_supported":["id","api","web","full","chatter_api",
"visualforce","refresh_token","openid","profile","email",
"address","phone","offline_access", "custom_permissions",
"wave_api", "eclair_api"],
"response_types_supported":["code","token","token id_token"],
"subject_types_supported":["public"],
"id_token_signing_alg_values_supported":["RS256"],
"display_values_supported":["page","popup","touch"],
"token_endpoint_auth_methods_supported":["client_secret_post","client_secret_basic",
"private_key_jwt"]
"claims_supported": ["active","address","email","email_verified","family_name",
"given_name","is_app_installed","language","locale","name","nickname",
"organization_id","phone_number","phone_number_verified","photos",
"picture","preferred_username","profile","sub","updated_at","urls","user_id",
"user_type","zoneinfo"], } 
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.