#
Configuring HTTPS in Core Server
#
Configuring Site Bindings
Open the File Explorer and navigate to the
C:\Program Files\OpeniT\Core\Configuration\httpd\Caddyfiles\settings
folder.Right-click on the
site-bindings.caddy
file.Select Open with and choose a text editor of your choice (e.g., Notepad, Sublime Text, etc.).
Update the (site-bindings) block using the syntax:
import <type>.template "<host>" "<port>"
Site Bindings Parameters
Exampleimport http.template "samplehost" "8080"
To add site bindings with automatic certificate creation, add auto- before the type.
Exampleimport auto-https.template "server1.cloud.com" "443"
Save the changes.
Navigate to the
/var/opt/openit/httpd/Caddyfiles/settings
directory.Edit
site-bindings.caddy
file.Update the (site-bindings) block using the syntax:
import <type>.template "<host>" "<port>"
Site Bindings Parameters
Exampleimport http.template "samplehost" "8080"
To add site bindings with automatic certificate creation, add auto- before the type.
Exampleimport auto-https.template "server1.cloud.com" "443"
Save the changes.
#
Configuring HTTPS with SSL Certificate and Key Extracted from PFX Certificate
The Open iT Core Server can use secure browsing(HTTPS) using either an SSL certificate and SSL key or a reverse proxy.
This section provides steps on extracting and using SSL certificate(.crt
) and SSL key(.key
) for secure browsing in case only a .pfx
certificate is available.
Open a command prompt with Administrator level privileges.
Go to the directory where the
.pfx
certificate is (e.g.,C:\Users\openit\Documents\openit_pfx
).Extract the private
.key
file from the certificate using openssl by running the following:"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" pkcs12 -in <pfx_cert_path_and_filename> -nocerts -out <output_file>
Where:
<pfx_cert_path_and_filename> is the path to the
.pfx
certificate.<output_file> will be the name of the private
.key
file.
Example"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" pkcs12 -in certificate.pfx -nocerts -out private.key
When prompted for the import password, type the password used to protect the keypair when the
.pfx
file is created. Provide a new password to protect the.key
file being created. Store the password of the key file in a secure place to avoid misuse.Extract the .
crt
file from the certificate using openssl by running the following:"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" pkcs12 -in <pfx_cert_path_and_filename> -clcerts -nokeys -out <output_file>
Where:
<pfx_cert_path_and_filename> is the path to the
.pfx
certificate.<output_file> will be the name of the
.crt
file.
Example"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" pkcs12 -in certificate.pfx -clcerts -nokeys -out server.crt
Decrypt the generated private key by running the following:
"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" rsa -in <private_key_file> -out <output_file>
Where:
<private_key_file> is the path to generated private
.key
.<output_file> will be the name of the
.key
file.
Example"C:\Program Files\OpeniT\Core\External\Apache\bin\openssl.exe" rsa -in private.key -out server.key
Go to the directory where the
.pfx
certificate is and verify that the.crt
and.key
files are created.Generated Certificates
Copy
server.crt
toC:\Program Files\OpeniT\Core\Configuration\httpd\ssl.crt
.Copy Certificate
Copy
server.key
toC:\Program Files\OpeniT\Core\Configuration\httpd\ssl.key
.Copy Decrypted Key
Restart the OpeniTReverseProxy service.
#
Configuring HTTPS using Let's Encrypt
This section provides steps for using Let's Encrypt to enable secure browsing.
Go to
C:\Program Files\OpeniT\Core\Configuration\httpd\Caddyfiles\settings
and openauto-https.template
in a text editor.https.template file
Provide the Core Server URL and port on line 1.
auto-https.template1|https://{args.0}:{args.1} { 2| import main 3|}
Example1|https://customer.domain.com:443 { 2| import main 3|}
Save the changes.
Restart the OpeniTReverseProxy service.
#
Next Steps?
After configuring HTTPS, the following steps are recommended but not required.