docs: add credential verification guidance for Docker installs

[brynsofz]

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

• Confirm you have read the contribution guidelines
• You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
• Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

• There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
• The issue connected to the PR must have Labels and Milestone assigned
• PR for bug fixes and small new features are presented as a single commit
• PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
• New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @brynsofz on file. In order for us to review and merge your code, please contact the project maintainers to get yourself added.

[gemini-code-assist]

Code Review

This pull request updates the GeoNode documentation to guide users on verifying and securing credentials, handling randomly generated passwords, and fixing broken links. The review feedback correctly identifies two critical issues in the hardening instructions: first, changing the GeoServer admin password via the UI without updating the .env file will break integration; second, using docker compose restart fails to reload updated .env variables, so containers should be recreated using docker compose up -d instead.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If you change the GeoServer admin password via the GeoServer Web UI, you must also update the GEOSERVER_ADMIN_PASSWORD variable in your .env file and recreate the Django container. Otherwise, GeoNode will be unable to authenticate with GeoServer using the old password, which will break core integration features such as layer uploads, map creation, and catalog synchronization. Please update the instructions to include updating the .env file and recreating the containers.

[gemini-code-assist]

Using docker compose restart does not reload the .env file or recreate the containers with the updated environment variables. As a result, the containers will continue to run with the old OAUTH2_CLIENT_ID and OAUTH2_CLIENT_SECRET values, while the database has the new ones, causing OAuth2 authentication to fail. To apply changes made to the .env file, you should recreate the containers using docker compose up -d instead.