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
Copy file name to clipboardExpand all lines: source/auth/auth.rst
+1-7Lines changed: 1 addition & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1120,20 +1120,14 @@ be used in lieu of manual caching.
1120
1120
1121
1121
If using manual caching, the "Expiration" field MUST be stored
1122
1122
and used to determine when to clear the cache. Credentials are considered
1123
-
valid if they are more than one minute away from expiring, to the reduce the
1123
+
valid if they are more than five minutes away from expiring, to the reduce the
1124
1124
chance of expiration before they are validated by the server.
1125
1125
1126
1126
If there are no current valid cached credentials, the driver MUST initiate a
1127
1127
credential request. To avoid adding a bottleneck that would override the
1128
1128
``maxConnecting`` setting, the driver MUST not place a lock on making a
1129
1129
request. The cache MUST be written atomically.
1130
1130
1131
-
Once valid credentials are received, the driver SHOULD schedule an update of
1132
-
the cache within five minutes of the expiration time, unless the driver does not have the ability to schedule background tasks. The background task MUST
1133
-
handle timeouts or errors and retry appropriately. The purpose of the
1134
-
background task is to limit the chance of needing to initiate multiple
1135
-
simultaneous requests.
1136
-
1137
1131
If AWS authentication fails for any reason, the cache MUST be cleared.
0 commit comments