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

Add context when changing secret_key_base #47723

Merged
merged 1 commit into from
Apr 5, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 8 additions & 1 deletion guides/source/security.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,14 @@ In test and development applications get a `secret_key_base` derived from the ap
secret_key_base: 492f...
```

WARNING: If your application's secrets may have been exposed, strongly consider changing them. Changing `secret_key_base` will expire currently active sessions.
WARNING: If your application's secrets may have been exposed, strongly consider
changing them. Note that changing `secret_key_base` will expire currently active
sessions and require all users to log in again. In addition to session data, the
following things may also be affected:

* Encrypted cookies
* Signed cookies
* Active Storage Files

### Rotating Encrypted and Signed Cookies Configurations

Expand Down