Difference between revisions of "SSL Configuration using Certificate"
(→Install PFX certificates) |
(→Install PFX certificates) |
||
Line 60: | Line 60: | ||
== Install PFX certificates == | == Install PFX certificates == | ||
+ | |||
+ | As regards certificates with the .pfx or .p12 extension, there is no need to convert them, because they are certificate archives already supported by Tomcat. | ||
Modify the value of the Connector attribute in the server.xml file to the following: | Modify the value of the Connector attribute in the server.xml file to the following: | ||
Line 76: | Line 78: | ||
/> | /> | ||
</source> | </source> | ||
+ | Save the file and access the address via browser https://YourServerDomain:8443 by replacing 'YourServerDomain' with | ||
+ | the actual domain of your server. | ||
This procedure works for both certificate files with the .pfx extension and those with the .p12 extension | This procedure works for both certificate files with the .pfx extension and those with the .p12 extension |
Revision as of 15:12, 27 February 2024
LogicalDOC embeds the Tomcat application server and it can be configured to support the encrypted protocol HTTPS. This is useful when you want to expose the program on the Internet.
Please be aware that this procedure is not coverded by the standard support contract. In case you want this matter to be handled professionally, please write to sales@logicaldoc.com for a quote. |
Basically you only have to follows the steps described in the Apache how-to at SSL Configuration HOW-TO What follows is a re-visioned extract from that how-to
Preparing the certificates
Note: skip this step if you already have your own SSL certificate
To install and configure SSL support on Tomcat, you need the following things:
- The file of your server certificate (the format must be PEM-encoded)
- The file containing the certificate chain associated with the server certificate (the format must be PEM-encoded)
- The file that contains the server private key (the format must be PEM-encoded)
You get those 3 files as a result of the certificate issuing procedure.
Most of the times you server's certificate and the chain file are in .crt, .cer or .der format.
In this case please convert them openssl:
openssl x509 -in cert.crt -out cert.pem
openssl x509 -in cert.cer -out cert.pem
openssl x509 -in cert.der -out cert.pem
In the same way, probably your secret key is in .txt format, so please convert it into .pem using openssl:
openssl rsa -in privkey.txt -out privkey.pem
We suggest to put your .pem files in <LDOC_HOME>/conf and in any case outside the tomcat folder.
Edit the Tomcat configuration file
The final step is to configure your secure socket in the <LDOC_HOME>/tomcat/conf/server.xml file, where <LDOC_HOME> represents the base directory for the LogicalDOC installation. An example <Connector> element for an SSL connector looks something like this:
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="8443" maxThreads="200"
URIEncoding="UTF-8" server="Undisclosed/8.41"
scheme="https" secure="true" SSLEnabled="true">
<SSLHostConfig>
<Certificate certificateFile="${catalina.home}/../conf/<b>cert.pem</b>"
certificateKeyFile="${catalina.home}/../conf/<b>privkey.pem</b>"
certificateChainFile="${catalina.home}/../conf/<b>chain.pem</b>" />
</SSLHostConfig>
</Connector>
replace <LDOC_HOME> with the installation path of LogicalDOC
The port attribute (default value is 8443) is the TCP/IP port number on which Tomcat will listen for secure connections. You can change this to any port number you wish.
If you change the port number here, you should also change the value specified for the redirectPort attribute on the non-SSL connector. This allows Tomcat to automatically redirect users who attempt to access a page with a security constraint specifying that SSL is required.
After completing these configuration changes, you must restart LogicalDOC as you normally do, you should be able to access via SSL. For example, try:
https://localhost:8443
and you should see the usual login page.
Install PFX certificates
As regards certificates with the .pfx or .p12 extension, there is no need to convert them, because they are certificate archives already supported by Tomcat.
Modify the value of the Connector attribute in the server.xml file to the following:
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="8443" maxThreads="200"
URIEncoding="UTF-8" server="Undisclosed"
maxHttpHeaderSize="16384"
scheme="https" secure="true" SSLEnabled="true"
clientAuth="false"
sslProtocol="TLSv1.1+TLSv1.2+TLSv1.3"
keystoreFile="${catalina.home}/../conf/mycert.pfx" # Path of the certificate file
keystoreType="PKCS12"
keystorePass="certpasswd" # Replace the value with the password of your certificate
/>
Save the file and access the address via browser https://YourServerDomain:8443 by replacing 'YourServerDomain' with the actual domain of your server.
This procedure works for both certificate files with the .pfx extension and those with the .p12 extension