Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change to AcquireToken to have refresh tokens cached properly #37

Merged
merged 4 commits into from
Feb 3, 2016
Merged

Change to AcquireToken to have refresh tokens cached properly #37

merged 4 commits into from
Feb 3, 2016

Conversation

peternied
Copy link
Contributor

No description provided.

Peter Nied added 4 commits February 2, 2016 16:10
Fixes #36
When using the AquireTokenByRefreshToken(...) method, the underlying ADAL
system does not guarentee the token will be saved for future use in the
TokenCacheStore.  Tracing into the AuthenticationContext implementation,
refreshToken(..., final boolean useCache) is getting set to false in all
of the 'refresh token` scenarios.  Using aquireToken and then depending on
the Prompt settings seems to be the best course of action to mitigate this
issue.  Note: it is not clear why this behavoir changed.
Noticed that we were missing some information from the logs when looking
at traces, adding those details to speed up turn around time.
peternied pushed a commit that referenced this pull request Feb 3, 2016
Change to AcquireToken to have refresh tokens cached properly
@peternied peternied merged commit 585fb5a into OneDrive:master Feb 3, 2016
@peternied peternied deleted the SilentAuth branch February 3, 2016 00:48
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants