Follow the token.

A hands-on course in identity and OAuth for Salesforce people. Six levels, from what a token is to how an artificial intelligence (AI) agent acts on someone's behalf.

Every integration and agent design comes down to the same questions: who is calling, on whose behalf, and with what permission. Agentforce agents acting for a user, Named Credentials calling external application programming interfaces (APIs), single sign-on into Salesforce, and Model Context Protocol (MCP) tool calls all rest on identity and OAuth. You can't design, troubleshoot or explain them to a customer without that foundation, and this course builds it from the ground up.

Access token journey visualization Browser Identity provider App API Access token
0

Vocabulary and mental model

Authentication vs. authorization; identity provider, service provider, resource server; ID, access and refresh tokens; how a JavaScript Object Notation (JSON) Web Token (JWT) is built and why its signature makes it trustworthy.

Lab: Get a token from your own org and decode it on your computer.

Start Level 0
1

Single sign-on: Security Assertion Markup Language (SAML) and OpenID Connect (OIDC)

What happens during a login redirect; how Federation ID ties a Microsoft Entra user to a Salesforce user.

Lab: Inspect a real SAML assertion and an OIDC ID token with Keycloak.

Start Level 1
2

OAuth 2.0 core flows, with Salesforce as the authorization server

The four roles;[1]§1.1 authorization code with Proof Key for Code Exchange (PKCE), client credentials, refresh, JWT bearer, device; External Client Apps.

Lab: Run each flow live against a hosted Keycloak instance.

Start Level 2
3

Salesforce as the OAuth client

Named Credentials, External Credentials, Auth Providers; named principal vs. per-user principal.

Lab: Call Microsoft Graph from Salesforce both ways.

Start Level 3
4

The hard parts

Scopes vs. app roles, consent, on-behalf-of, token exchange (Request for Comments (RFC) 8693), workload identity federation; briefly, sender-constrained tokens (mutual Transport Layer Security (mTLS), Demonstrating Proof of Possession (DPoP)).

Lab: Build the patterns you'll need for complex enterprise scenarios.

In development

5

Agent identity (capstone)

Agentforce run-as users, Agent API authentication, MCP's OAuth model, Agent2Agent (A2A), Microsoft Entra Agent ID.

Deliverable: A full answer to a real customer's question about giving Agentforce agents an identity in Entra ID, backed by working labs.

In development

What you'll need

  • A Salesforce dev org (free at developer.salesforce.com)
  • A Microsoft Entra tenant you control (a free Azure account creates one; the Microsoft 365 Developer Program sandbox is now mostly limited to Visual Studio subscribers)
  • A Salesforce developer experience (DX) project, from Level 2

Sources

  1. RFC 6749: The OAuth 2.0 Authorization Framework, Section 1.1, IETF