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
{{ message }}
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.
Which Version of ADAL are you using ?
latest (5.2.5)
Which platform has the issue?
xamarin android
What authentication flow has the issue?
Desktop / Mobile
Interactive
Silent
Integrated Windows Auth
Username Password
Device code flow (browserless)
Web App
Authorization code
OBO
Web API
OBO
Repro
Make an interactive call using broker on android for one resource and then try to acquire a token silently for a different resource.
Expected behavior
Broker should be able to successfully refresh the token Actual behavior
The app is forced to sign in interactively again and broker throws the following error
"Could not locate a cache for this app"
Possible Solution
We need to send the UID instead of the PID that we send today because the UID will not change for the user on the device. The broker uses the UID to cache responses so if the UID changes for any reason the cache lookup will fail.
The text was updated successfully, but these errors were encountered:
Which Version of ADAL are you using ?
latest (5.2.5)
Which platform has the issue?
xamarin android
What authentication flow has the issue?
Repro
Make an interactive call using broker on android for one resource and then try to acquire a token silently for a different resource.
Expected behavior
Broker should be able to successfully refresh the token
Actual behavior
The app is forced to sign in interactively again and broker throws the following error
"Could not locate a cache for this app"
Possible Solution
We need to send the UID instead of the PID that we send today because the UID will not change for the user on the device. The broker uses the UID to cache responses so if the UID changes for any reason the cache lookup will fail.
The text was updated successfully, but these errors were encountered: