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
This allows users to override the default expiry behavior when using
DynamoDB TTL to expire sessions from the table. This would be useful,
for example, if they wanted to use a browser session scoped cookie as
the session cookie (with no maxAge attribute) but needed a shorter TTL
than the default '1 day from now'.
If this parameter is not provided then there will be no change to the
current behaviour.
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ unless the `client` options is provided to override them.
21
21
☣️ Legacy reap behaviors use DynamoDB [`scan`](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-dynamodb/classes/scancommand.html)
22
22
functionality that can incur significant costs. Should instead enable [DynamoDB TTL](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html)
23
23
and select the `expires` field. TODO should we just remove it since we're already making a breaking change?
24
+
-`expiresIn` Optional set the number of seconds for DynamoDB TTL. Defaults to the cookie's maxAge.
24
25
25
26
## Usage
26
27
@@ -42,6 +43,8 @@ var options = {
42
43
],
43
44
// Optional skip throw missing special keys in session, if set true
44
45
skipThrowMissingSpecialKeys:true,
46
+
// Optional set the number of seconds for DynamoDB TTL
0 commit comments