You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling tokenAcquirerFactory.GetTokenAcquirer from multiple thread, behavior wasn't uncertain as the underlying datastructure is a non thread safe dictionary.
Additionally, when calling tokenAcquirerFactory.GetTokenAcquirer passing differnet regions, only one tokenAcquirer is ever created and returned.
Reproduction steps
Call TokenAcquirerFactory.GetTokenAcquirer passing US as the region
Call TokenAcquirerFactory.GetTokenAcquirer passing EU as the region
The US TokenAcquirer is returned again instead of creating a new EU regioned TokenAcquirer.
Microsoft.Identity.Web Library
Microsoft.Identity.Web
Microsoft.Identity.Web version
2.17.4
Web app
Sign-in users and call web APIs
Web API
Protected web APIs (validating tokens)
Token cache serialization
Not Applicable
Description
When calling tokenAcquirerFactory.GetTokenAcquirer from multiple thread, behavior wasn't uncertain as the underlying datastructure is a non thread safe dictionary.
Additionally, when calling tokenAcquirerFactory.GetTokenAcquirer passing differnet regions, only one tokenAcquirer is ever created and returned.
Reproduction steps
The US TokenAcquirer is returned again instead of creating a new EU regioned TokenAcquirer.
Error message
No response
Id Web logs
No response
Relevant code snippets
Regression
No response
Expected behavior
A new TokenAcquirer should be returned for each region:
The text was updated successfully, but these errors were encountered: