Skip to content

Commit d777502

Browse files
committed
Add documentation of JWT_COOKIE_PARTITIONED flag.
1 parent 7392892 commit d777502

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

docs/options.rst

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@ Overview:
4444
* `JWT_COOKIE_DOMAIN`_
4545
* `JWT_COOKIE_SAMESITE`_
4646
* `JWT_COOKIE_SECURE`_
47+
* `JWT_COOKIE_PARTITIONED`_
4748
* `JWT_REFRESH_COOKIE_NAME`_
4849
* `JWT_REFRESH_COOKIE_PATH`_
4950
* `JWT_SESSION_COOKIE`_
@@ -358,6 +359,18 @@ These are only applicable if a route is configured to accept JWTs via cookies.
358359

359360
Default: ``False``
360361

362+
.. _JWT_COOKIE_PARTITIONED:
363+
.. py:data:: JWT_COOKIE_PARTITIONED
364+
365+
Controls if the ``partitioned`` flag should be placed on cookies
366+
created by this extension.
367+
368+
Cookies Having Independent Partitioned State (CHIPS, also known as
369+
Partitioned cookies) allows developers to opt a cookie into
370+
partitioned storage, with a separate cookie jar per top-level
371+
site.
372+
373+
Default: ``False``
361374

362375
.. _JWT_REFRESH_COOKIE_NAME:
363376
.. py:data:: JWT_REFRESH_COOKIE_NAME

0 commit comments

Comments
 (0)