DPoP proof JWT on API calls (without nonce)#4060
Draft
sfdctaka wants to merge 6 commits into
Draft
Conversation
bbirman
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new public, ObjC-visible property to SFOAuthCredentials:
@property (nonatomic, readonly, nullable) NSString *tokenType;Why: the OAuth token endpoint (RFC 6749 §5.1) returns a token_type field — "Bearer" or "DPoP" — which determines the Authorization scheme the SDK must use on subsequent authenticated requests. The DPoP rollout requires the SDK to read this value, persist it across launches, and gate scheme selection on it. Existing tokenFormat is a Salesforce-specific field ("jwt"/"opaque") and is not the right signal.
Storage and lifecycle: tokenType is encoded/decoded in NSCoder, copied in
copyWithZone:, cleared onrevokeRefreshToken, and parsed inupdateCredentials:from the token_type response key. It mirrors tokenFormat exactly.Consumers: read-only externally; populated only by the SDK's own token-endpoint response parser. Apps and ISVs do not need to set it.
Backward compatibility: purely additive. No existing API changes, no behavior change for non-DPoP orgs (Bearer remains
the default and is byte-identical to pre-DPoP output — verified by a regression snapshot test).