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.

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

Jump to bottom

Pull minor doc changes related to security into v4.6.1 app branch. #3689

Merged
merged 2 commits into from
Mar 13, 2017
Merged

Pull minor doc changes related to security into v4.6.1 app branch. #3689

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
24c6b4e
Update config.rst
kcondon Mar 10, 2017
fa9f0bc
Merge pull request #3688 from IQSS/v4.6.1-tweak-doc
kcondon Mar 13, 2017
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
10 changes: 10 additions & 0 deletions doc/sphinx-guides/source/installation/config.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,16 @@ Forcing HTTPS

To avoid having your users send credentials in the clear, it's strongly recommended to force all web traffic to go through HTTPS (port 443) rather than HTTP (port 80). The ease with which one can install a valid SSL cert into Apache compared with the same operation in Glassfish might be a compelling enough reason to front Glassfish with Apache. In addition, Apache can be configured to rewrite HTTP to HTTPS with rules such as those found at https://wiki.apache.org/httpd/RewriteHTTPToHTTPS or in the section on :doc:`shibboleth`.

Additional Recommendations
++++++++++++++++++++++++++

To further enhance the security of your installation, we recommend taking the following specific actions:

- Configure Glassfish to run as a user other than root.
- Remove /root/.glassfish/pass password files.
- Store passwords as a hash rather than base64 encoded. Ideally this will be a salted hash, and use a strong hashing algorithm.
- Use a strong administrator password so the hash cannot easily be cracked through dictionary attacks.

Solr
----

Expand Down