Propagate long running web API session key back to caller in user token acquisition flow#3728
Merged
cpp11nullptr merged 2 commits intoFeb 19, 2026
Conversation
…en acqisition flow
Member
|
@trwalke - pls review. |
trwalke
reviewed
Feb 18, 2026
trwalke
reviewed
Feb 18, 2026
trwalke
approved these changes
Feb 19, 2026
iNinja
approved these changes
Feb 19, 2026
cpp11nullptr
deleted the
iepoly/propagate-long-runinning-obo-session-key-for-user-token-acquisition
branch
This was referenced Mar 1, 2026
deps: Bump Microsoft.Identity.Web from 4.3.0 to 4.4.0
microsoft/dragon-copilot-extension-samples#173
Merged
Closed
Merged
This was referenced May 26, 2026
Closed
Closed
Merged
Open
This was referenced Jun 5, 2026
This was referenced Jun 14, 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
4 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.
When long running web API session is created with "AllocateForMe" session key, a new session key is auto-generated and set in
tokenAcquisitionOptions. This change propagates a new session key to caller ofTokenAcquirer::GetTokenForUserAsync()so consumer side can use this key to fetch cached token later.Note that CreateAuthorizationHeaderForUserAsync scenario already does it so no changes are needed there.