The following steps can be used to configure ELOG to use Secure Sockets Layer (SSL) for encrypted connectivity to the server. I.e. you can use Hypertext Transfer Protocol over Secure Socket Layer or HTTPS.
elogd.cfgfile with a text editor, such as Notepad, if you installed ELOG on a Windows system. On a Windows system, the file is installed by default in
C:\Program Files\ELOGIf it wasn't installed in the default location and you don't know where it was installed, you can use the instructions in ELOG Port Configuration to determine its location.
[global]section of the file:
SSL = 1
net stop elogd
net start elogd
You can then access the ELOG webserver by opening a web browser on the system
on which you've installed ELOG and pointing the browser to the loopback address
of the system, which is 127.0.0.1. I.e., you can use
https://127.0.0.1:8080, or you can use the fully qualified
domain name (FQDN) of the system on which ELOG was installed. E.g. you could
https://a.example.com:8080, if the system was named
a.example.com and you are using the default port for ELOG,
You will get a warning message from your browser regarding the security
certificate, because it is self-signed rather than being
signed by a recognized certificate issuing entity. You can continue without
worrying about the certificate, however. The self-signed ELOG security
certificate is in the ELOG
ssl directory. You can purchase
a certificate from a recognized certification entity to avoid browser
warnings about the certificate. If you perform a web search on
"purchase SSL certificate" you will get lots of links to places where you can
purchase an authenticated certificate.
By default you can connect to the ELOG webserver from other addresses, i.e. you aren't limited to just accessing it from the system on which it was installed, unless you have a firewall blocking access to the address, in which case you will need to allow access by configuring an appropriate firewall rule.
Created: Sunday August 3, 2008