Headless Identity Implementation Guide

What Is Headless Identity?
Complete Prerequisites for Headless Identity
Set Up an Authentication Provider for Single Sign-On
Set Up an Experience Cloud Site for Headless Identity
Set Up a Connected App for Headless Identity
Use Postman to Work with Headless Identity APIs
Set Up Your Postman Workspace
Headless Registration Flow: Send a Registration Request
Headless Registration Flow: Send an Authorization Request
Headless Registration Flow: Send a Token Request
Headless Login: Send an Authorization Request
Headless Login: Send a Token Request
Headless Registration and Headless Login Flows: Get User Info
Headless Forgot Password Flow: Send a Password Reset Request
Headless Forgot Password Flow: Change the User’s Password
Headlessly Revoke an Access Token
JavaScript Examples for Headless Identity APIs
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Set Up Your Postman Workspace

To get started with Postman, fork the public Salesforce Developers collection and set your variables.
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions

To work with this collection, you must have a Postman account that’s connected to Salesforce, meaning that the Salesforce Postman collection must be authorized to access your org. If you’re using Postman in a browser, you must also add the Postman URL patterns to your Cross-Origin Resource Sharing (CORS) allowlist. For instructions on completing these steps, see the Quick Start: Connect Postman to Salesforce Trailhead module.

If you’re using the Postman desktop app, you can skip configuring your CORS allowlist.

Note

  1. If you haven’t already, fork the Salesforce Platform APIs collection from the public Salesforce Developers workspace. By forking the collection, you can modify it on your local workspace without changing the parent version.
    1. Open the Salesforce Developers workspace.
    2. In Collections, select Salesforce Platform APIs, click Postman icon with three dots, and then select Create a Fork.
    3. Name the fork, add it to your workspace, and click Fork Collection.
  2. Reset the collection variables to use your own.
    1. Select the forked Salesforce Platform APIs collection in your workspace.
    2. Select the Variables tab.
      The variables here apply to the entire Salesforce Platform APIs collection, so only a few of them are relevant to this example. You can ignore the ones that aren’t.
    3. Replace the current value for url with your Experience Cloud site domain, such as MyExperienceCloudSite.my.site.com.
    4. Replace the current value for clientId with your connected app consumer key.
    5. Replace the current value for redirectUrl with https://MyExperienceCloudSite.my.site.com/services/oauth2/echo, where https://MyExperienceCloudSite.my.site.com is your Experience Cloud site domain. This value must match your connected app callback URL.
    The variable list also contains a site variable, which you can use to store an Experience Cloud site suffix if your site has one. For this example implementation, we didn’t add a suffix, so leave this value blank.
  3. To see the Headless Identity examples, expand the Salesforce Platform APIs collection, select Auth, and then select Headless Identity API Demo.