Add context when changing secret_key_base #47723
Merged
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.
Motivation / Background
The current documentation in https://github.com/rails/rails/blob/main/guides/source/security.md#L118 only mentions that changing
secret_key_base
will expire currently active sessions, but it does not list other things that will be affected such as encrypted cookies, signed cookies, and Action Text attachments.This Pull Request aims to add additional context to the documentation to better inform users of the potential impacts of changing the
secret_key_base
.Detail
N/A
Additional information
N/A
Checklist
Before submitting the PR make sure the following are checked:
[Fix #issue-number]