...
| Code Block |
|---|
|
# docker ps (To get the name of running container)
# docker exec -it qmetry8Xqmetry_qtmapp_1 bash (Login to docker container by replacing x with the version seen in above command)
# mkdir -p /opt/ssl
# cd /opt/ssl
# keytool -genkey -alias qmetry -keyalg RSA -keysize 2048 -keystore qtm_test_qmetry.jks
Enter keystore password: <This is the keystore password>
Re-enter new password: <This is the keystore password>
What is your first and last name?
[Unknown]: <Enter First Name and Last Name>
What is the name of your organizational unit?
[Unknown]: e.g QMetry
What is the name of your organization?
[Unknown]: e.g QMetry
What is the name of your City or Locality?
[Unknown]: e.g Santa Clara
What is the name of your State or Province?
[Unknown]: e.g San Francisco
What is the two-letter country code for this unit?
[Unknown]: e.g SF
Is CN=Firstname Lastname, OU=QMetry, O=QMetry, L=Santa Clara, ST=San Francisco, C=SF correct?
[no]: yes
Enter key password for <tomcat>
(RETURN if same as keystore password): <Just hit Enter to keep same password as keystore>
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore qtm_test_qmetry.jks -destkeystore qtm_test_qmetry.jks -deststoretype pkcs12".
|
Step 2: Generate
...
CSR
| Code Block |
|---|
|
# keytool -certreq -alias qmetry -file qtm_test_qmetry.csr -keystore qtm_test_qmetry.jks
Enter keystore password: <Enter Keystore Password as per Step 1>
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore qtm_test_qmetry.jks -destkeystore qtm_test_qmetry.jks -deststoretype pkcs12".
|
...
| Code Block |
|---|
|
# docker cp qtm_test_qmetry.p7b qmetry8Xqmetry_qtmapp_1:/opt/ssl (Copy qtm_test_qmetry.p7b to Docker's /opt/ssl directory)
# docker exec -it qmetry8Xqmetry_qtmapp_1 bash (Login to docker container by replacing x with the version seen in above command)
# cd /opt/ssl/
# keytool -import -alias qmetry -file qtm_test_qmetry.p7b -keystore qtm_test_qmetry.jks
Enter keystore password: <Enter Keystore Password as per Step 1>
-------
----
--
... is not trusted. Install reply anyway? [no]: yes
Certificate reply was installed in keystore
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore qtm_test_qmetry.jks -destkeystore qtm_test_qmetry.jks -deststoretype pkcs12".
|
...
| Code Block |
|---|
|
# exit (exit the docker container)
# docker stop qmetry8Xqmetry_qtmapp_1 (Replace x with
the version seen in : docker ps command)
# docker start qmetry8Xqmetry_qtmapp_1 (Replace x with the version seen in : docker ps
command)
|
After following the above steps QMetry would be accessible via https://domain.qmetry.com/
Step 12: Modify QMetry Settings to
...
HTTPS, ensure both QMetry and Reports servers have SSL certificates installed.
| Code Block |
|---|
|
Go to Profile >> Edit >> Base URL >> Change to https.
Go to Profile >> Edit >> Report Server URL >> Change to https. |
Step 13: Take the backup of the
...
SSL certificate to root directory
| Code Block |
|---|
|
# docker cp -a qmetry8Xqmetry_qtmapp_1:/opt/ssl /root/ (Replace x with the version seen in : docker ps command) |