Skip to Content

Changes for page Security

Last modified by Arthur Heffern on 2021/09/09 20:55
From version 4.1
edited by michelk
on 2021/09/09 18:02
Change comment: Import
To version 5.1
edited by Arthur Heffern
on 2021/09/09 18:02
Change comment: Import

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +iSymphony Administrator's Guide
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.michelk
1 +XWiki.arthurh
Tags
... ... @@ -1,0 +1,1 @@
1 +black|white|http|realm|authentication|auth|security|ssl|ip|list
Content
... ... @@ -92,10 +92,54 @@
92 92  {{/warning}}
93 93  )))
94 94  
95 -== Enabling And Disabling Security Contexts ==
95 +=== Creating a Keystore with Let's Encrypt ===
96 96  
97 -You can enable and disable entire **Security Contexts** by setting the **enabled** attribute to **true** or **false** in the **SecurityContext** tag. A disabled **Security Context** will apply no restrictions to the servlet despite any of the inner settings.
97 +{{note}}
98 +This section is a work in progress and will be updated.
99 +{{/note}}
98 98  
101 +==== Creating a Keystore with The Let's Encrypt module for FreePBX ====
102 +
103 +FreePBX automates the process for obtaining a Let'sEncrypt certificate and utilizes it's own directory structure and file names to place the resulting files (The Certificate, any intermediate Certificate Authority chain and private key) on the filesystem.
104 +
105 +First, we must compile and convert the resulting LE certificate chain and private key to PKCS12 format utilizing the OpenSSL binaries:
106 +
107 +{{code}}
108 +openssl pkcs12 -export -in /etc/asterisk/keys/<HOSTNAME>/fullchain.pem -inkey /etc/asterisk/keys/<HOSTNAME>/private.pem -name isymphony -out isymphony.pkcs12
109 +{{/code}}
110 +
111 +{{note}}
112 +Ensure you change the <HOSTNAME> placeholder above to reference the directory name that was created as part of the FreePBX certificate acquisition process.
113 +{{/note}}
114 +
115 +You can choose the name you would like for the certificate alias and resulting pkcs12 keystore file name (-name and -out parameters). The above is only an example, though works without issue, so feel free to use it if appropriate.
116 +
117 +The OpenSSL command will ask you for a password for the exported keystore. Be sure to set one as it is required and empty string passwords are not valid for this process. For this example, we used the password "isymphony".
118 +
119 +Then, you just import the resulting pkcs12 keystore into a newly created Java Keystore supplying the appropriate parameters and set the destination store password and key password:
120 +
121 +{{code}}
122 +keytool -importkeystore -deststorepass isymphony -destkeypass isymphony -destkeystore isymphony.jks -srckeystore isymphony.pkcs12 -srcstoretype PKCS12 -alias isymphony
123 +{{/code}}
124 +
125 +And your new java keystore will be in the resulting file: ./isymphony.jks file.
126 +
127 +This file should be copied into the top level directory of your **/opt/isymphony3/server/conf** (or appropriate installation directory for iSymphony) directory.
128 +
129 +== Make iSymphony Aware of the SSLKeystore ==
130 +
131 +Modify /opt/isymphony3/server/conf/security.xml to make iSymphony aware of the keystore by modifying the SSLKeystore XML element with the appropriate values:
132 +
133 +{{code}}
134 +<SSLKeystore filename="isymphony.jks" keystorePassword="isymphony" keyPassword="isymphony" certAlias="isymphony" />
135 +{{/code}}
136 +
137 +Then enabling SSL on each context you would like to utilize SSL (More on this below) and restarting the iSymphonyServerV3 service should complete the configuration.
138 +
139 +== Enabling And Disabling Security Context ==
140 +
141 +You can enable and disable entire **Security Contexts** by setting the **enabled** attribute to **true** or **false** in the **SecurityContext** tag in the **/opt/isymphony3/server/conf/security.xml** file. A disabled **Security Context** will apply no restrictions to the servlet despite any of the inner settings.
142 +
99 99  1. (((
100 100  == SSL ==
101 101  )))