MultipleTokensMatched exception when using standard TokenCache

We have a client and service application where the client sends a token Bearer

and we use this token on the service side to get AccessToken

for other services like an endpoint Graph

. We are using the default TokenCache obtained using AuthenticationContext. We are facing a AdalException(AdalError.MultipleTokensMatched)

server side issue . My question is:

1) The code is still in prototype and no one else is using the client or service besides me, how can I end up here?

2) What exactly does TokenCache

not mean ThreadSafe

, and are there any better TokenCache

service-side implementations that I can use rather than build from scratch and test.

{"multiple_matching_tokens_detected: The cache contains multiple matching tokens. Call AcquireToken, again providing more requirements (eg UserId)"}

+3
azure-active-directory adal


source to share


No one has answered this question yet

Check out similar questions:

6
Accessing the Azure Graph API as an app, not a user
4
Getting AccessToken from Azure Ad via UserName & Password
2
multiple_matching_tokens_detected with ADAL
1
Should TokenCache be used for offline connections using MSAL?
1
What are the sub and oid claims when receiving client_credentials tokens from an Azure AD OAuth v2 token endpoint?
1
Obtaining a valid bearer token for an application from an AD Angular client
1
Active Directory Authentication Library Programmatic SSO
1
multiple_matching_tokens_detected exception in authContext.AcquireTokenAsync
0
Azure App Sevice authentication not working with bearer token (service to service)
0
MSAL: AcquireTokenSilentAsync always communicates with endpoint



All Articles
Loading...
X
Show
Funny
Dev
Pics