src

Refactor how token refreshing works to be more resilient (#4819)

Michael Telatynski authored 3 months ago and GitHub committed 3 months ago

* Refactor how token refreshing works to be more resilient

1. ensure we do use the new token if it is not explicitly inhibited by the caller
2. eagerly refresh token if we know it is expired
3. allow refreshing a token multiple times if e.g. on bad connection or the environment has been slept and sufficient time has passed since the last refresh attempt

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Iterate

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Iterate

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Add exponential backoff

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Ensure no timing effects on `authedRequest` method call

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Iterate

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

---------

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

d67b19fa

History

d67b19fa 3 months ago

History

Name	Last commit	Last update
..
@types
common-crypto
crypto-api
crypto/store
extensible_events_v1
http-api
matrixrtc
models
oidc
rendezvous
rust-crypto
store
utils
webrtc
NamespacedValue.ts
ReEmitter.ts
ToDeviceMessageQueue.ts
autodiscovery.ts
base64.ts
browser-index.ts
client.ts
content-helpers.ts
content-repo.ts
digest.ts
embedded.ts
errors.ts
event-mapper.ts
feature.ts
filter-component.ts
filter.ts
index.ts
indexeddb-helpers.ts
indexeddb-worker.ts
interactive-auth.ts
logger.ts
matrix.ts
pushprocessor.ts
randomstring.ts
realtime-callbacks.ts
receipt-accumulator.ts
room-hierarchy.ts
scheduler.ts
secret-storage.ts
serverCapabilities.ts
service-types.ts
sliding-sync-sdk.ts
sliding-sync.ts
sync-accumulator.ts
sync.ts
testing.ts
thread-utils.ts
timeline-window.ts
types.ts
utils.ts
version-support.ts