docs: correct session signing terminology - #96986
Open
Fastering18 wants to merge 1 commit into
Open
Conversation
Fastering18
marked this pull request as ready for review
August 9, 2026 05:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates the authentication docs to use the correct terminology for session handling.
The previous wording mixed up encryption with signing. Database sessions hand the browser a signed token that holds the session ID, not an encrypted one. The steps and section headings now talk about signing and verifying session data instead of encrypting and decrypting it.
A short note was also added to clarify that signing only stops undetected changes; it does not hide the data, so sensitive information should stay out of the payload.