Uh oh!
There was an error while loading. Please reload this page.
Adding fix for OBO cache key error in long running OBO with DefaultAuthorizationHeaderProvider - #3381
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Jean-Marc Prieur (jmprieur)
left a comment
There was a problem hiding this comment.
Wouldn't it be better to use the new interface that Keegan created:
this way we could return something?
I'm am not sure it is the best way to do it. The returning of the cache key also happens when using the See https://github.com/AzureAD/microsoft-identity-web/wiki/get-token-in-event-handler#principle Lets fix this for the customer since it is the currently released behavior and change the design in a follow up PR. I can create a work item. |
Description
Updates the
DefaultAuthorizationHeaderProviderto update theAcquireTokenOptions.LongRunningWebApiSessionKeyafter the token is acquired so that the key can be used in the next OBO call.Fixes#3382