2 |
Open the file <foglight_home>/config/server.config on the Management Server machine. |
3 |
Set the java system property foglight.credentials.enc.key.size to 256 (or higher): |
4 |
If you do not choose to install Foglight in Secure Server mode, you can edit server.config after installation and manually configure Foglight to restrict the Management Server to use the HTTPS port when accessing the browser interface.
You must have a signed, valid certificate to use this HTTPS configuration. It is recommended that you obtain a valid certificate from a third party as outlined in Importing a network security certificate.
2 |
Open the file <foglight_home>/config/server.config on the Management Server machine. |
3 |
4 |
5 |
7 |
Launch the Foglight browser interface using the appropriate HTTPS URL (https://<hostname>:<https_port>) to ensure that the Management Server can be accessed using HTTPS. |
<foglight_home>/jre/bin/keytool
There are two keystores that Foglight uses:
• |
The built-in Tomcat™ keystore located at: <foglight_home>/config/tomcat.keystore (default password: nitrogen) |
• |
The Management Server keystore located at: <foglight_home>/jre/lib/security/cacerts (default password: changeit) |
1 |
Back up the existing tomcat key using the following command: |
2 |
3 |
Create a new key under the tomcat alias using the following command: |
5 |
Once you have the certificate signed, import it back to the tomcat.keystore using the following command: |
You can configure the length of inactive Foglight browser interface sessions by changing the value of the parameter server.console.session.timeout. This parameter controls the length of time that Foglight waits before automatically logging you out of an idle browser interface session.
1 |
Stop the Management Server.Open the file <foglight_home>\config\server.config on the Management Server machine. Set the parameter server.console.session.timeout to the desired value in minutes. |
2 |
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center