Skip to content

Document the signing secret in Multiple App Servers #12435 #12673

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.

Sign up for GitHub

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

Merged
pdurbin merged 1 commit into from
Sep 9, 2026
+1 −0
Merged

Document the signing secret in Multiple App Servers #12435 #12673

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions doc/sphinx-guides/source/installation/advanced.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ You should be conscious of the following when running multiple app servers.
- If Make Data Count is used, its raw logs must be copied from each app server to single instance of Counter Processor. See also :ref:`:MDCLogPath` section in the Configuration section of this guide and the :doc:`/admin/make-data-count` section of the Admin Guide.
- Dataset draft version logging occurs separately on each app server. See :ref:`edit-draft-versions-logging` section in Monitoring of the Admin Guide for details.
- Password aliases (``dataverse.db.password``, etc.) are stored per app server.
- Each app server generates its own signing secret at startup unless one is configured, so a signed URL created on one server cannot be validated on another (and no signed URL survives a restart). Set :ref:`dataverse.api.signing-secret` to the same value (at least 36 characters) on every app server if you use signed URLs.

Detecting Which App Server a User Is On
+++++++++++++++++++++++++++++++++++++++
Expand Down