Skip to content
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

Extends the IP documentation #1258

Merged
merged 2 commits into from
Apr 25, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions docs/source/operators/security.rst
Original file line number Diff line number Diff line change
Expand Up @@ -147,8 +147,7 @@ Other required fields will be filled with `None`.
Identity Model
^^^^^^^^^^^^^^

The identity model is the model accessed at `/api/me`,
and describes the currently authenticated user.
The identity model is the model accessed at `/api/me`, and describes the currently authenticated user.

It has the following fields:

Expand Down Expand Up @@ -179,6 +178,20 @@ color
such as for collaboration cursors.
May be `null` if unavailable.


The default implementation of the identity provider is stateless, meaning it doesn't store user information
on the server side. Instead, it utilizes session cookies to generate and store random user information on the
client side.

When a user logs in or authenticates, the server generates a session cookie that is stored on the client side.
This session cookie is used to keep track of the identity model between requests. If the client does not
support session cookies or fails to send the cookie in subsequent requests, the server will treat each request
as coming from a new anonymous user and generate a new set of random user information for each request.

To ensure proper functionality of the identity model and to maintain user context between requests, it's
important for clients to support session cookies and send it in subsequent requests. Failure to do so may
result in the server generating a new anonymous user for each request, leading to loss of user context
Zsailer marked this conversation as resolved.
Show resolved Hide resolved

Authorization
*************

Expand Down