Differences

This shows you the differences between two versions of the page.

--- ssl_configuration [2019/01/18 14:38] – lucy
+++ ssl_configuration [2019/03/01 15:31] – lucy
@@ Line 26: / Line 26: @@
 {{ ssl_campaign.png?600 }}
-  * **SSL for E-Learning:**: Please gp to "awareness settings" within your campaign and then within the according scenario settings of your awareness template select the SSL options:
+  * **SSL for E-Learning:**: Please go to "awareness settings" within your campaign and then within the according to scenario settings of your awareness template select the SSL options:
 {{ awarw_ssl.png?600 }}
@@ Line 57: / Line 57: @@
   * https://www.gogetssl.com/online-csr-generator/
-After the verification, (most providers will either do a verification by sending an email to the email address within the WHOIS record or to the email specified within the CSR) you will have to upload the certificate to LUCY.
+After the verification, (most providers will either do verification by sending an email to the email address within the WHOIS record or to the email specified within the CSR) you will have to upload the certificate to LUCY.
 As an alternative: LUCY enables you to create a CSR by clicking "Generate CSR or Certificate".
@@ Line 74: / Line 74: @@
 {{ ssl_gen_2.png?direct&600 }}
-**Note**: If you want to get an official certificate for free, you can always use trial certificates which are valid for 90 days (example : https://www.comodo.com/e-commerce/ssl-certificates/free-ssl-certificate.php)
+**Note**: If you want to get an official certificate for free, you can always use trial certificates which are valid for 90 days (example: https://www.comodo.com/e-commerce/ssl-certificates/free-ssl-certificate.php)
@@ Line 89: / Line 89: @@
 (!) Please take into account that the command above will delete **all** existing SSL certificates!
-b. For Lucy __4.3 and newer version__ this could have happened after the migration from the version 4.2 via the Migration Tool. In that case please contact our support team (<support@lucysecurity.com>) to fix the issue.
+b. For Lucy __4.3 and newer version__ this could have happened after the migration from version 4.2 via the Migration Tool. In that case please contact our support team (<support@lucysecurity.com>) to fix the issue.