-
Notifications
You must be signed in to change notification settings - Fork 140
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
Preemptive Credentials refresh [SDK-1819] #349
Comments
Hey @skjolber ! 👋 If I understand correctly what you're asking, you need the "Credentials Managers" to expose some way to manually refresh the tokens, even when they have not expired yet and shouldn't be refreshed. Is that correct? If that's the case, one of the solutions we implemented in iOS and want to bring to Android as well is passing some TTL value on the Would a solution like that work for you? If so, I can link this issue to that card. |
That is right. Yes, I think the TTL approach you're describing will work for us 👍 |
Excellent. Tracking under |
@skjolber the 2 PRs above add support for this in both credential managers. I'll have it released in the next minor. |
Feature added in PRs 363 and 369 |
Describe the problem you'd like to have solved
We're building a ticket inspection app. We want to avoid interaction with the authorization server as much as possible during the inspection session, which can last from a few minutes to a few hours (all limited by the authorization server settings).
Describe the ideal solution
We would like preemptively refresh the access-token, and/or trigger a new (manual) login if the refresh-token is about to expire. Ideally some kind of
forceRefresh
parameter could be added and we would get the relevant timestamps fromCredentials
.Alternatives and current work-arounds
Get the credentials, look at the id-token expire time, clear them if not acceptable.
Additional context
SecureCredentialsManager
The text was updated successfully, but these errors were encountered: