Since we have to enable SSL on CQ server as well please notice the steps below are very important and will not be found in the nf file shown above.ħ You need to manually create those tags, therefore copy the TAG shown below in the nf file This is for CQ-Author: incoming vip for https (This is to secure CQ-Author server) ip address that resolves to the ConnectProHost (Web App FQDN). So in Total ( Application Server, Meeting Server, CQ-Author Server and CQ-Publish Server)Ħ Below you will see a regular nf file with application server and meeting server TAG CONSIDERING THAT WE ARE USING 4 IP ADDRESSES AND ONE WILD CARD CERTIFICATE Set application server on IP Address one (accept =IP-One:443) Set meeting server on IP Address Two (accept=ip-two:443) Set the certificates and Key names in both the Servers as marked in the figure above. Reason being we have 2 separate servers individually under the CQ server (CQ-Author Server and CQ-Publish Server). Similarly for securing CQ server as well, we must have in total 4 IP addresses 4 certificates in-case you are not using the wild card certificate. This is simpler to manage, but typically costs more than a single domain name certificate. (You may also get a single, wildcard SSL certificate that can be used for multiple hosts in the same sub-domain, e.g. On a single server, to secure both the HTTP (application server) and RTMP (meeting server) connections, you must have a total of two IP addresses, two FQDNs and two SSL certificates (one for each protocol). Note: In a cluster, all the application servers can share an SSL certificate, but each meeting server must have its own SSL certificate. Enter this FQDN in the External Name box on the Server Settings page in the Application Management Console. However, you must define a unique domain name for each meeting server if you want to conduct meetings over a secure connection. End users do not see the FQDN(s) for the meeting server(s). Enter this domain name as the Connect Host value on the Server Settings page in the Application Management Console. The domain name for the Central application server is the address with which your end users will access Adobe Connect with. If you intend to secure traffic for both the application server and the meeting server, you must have a separate IP address for each service. Configure the DNS server Create DNS entries that define addresses for the Fully Qualified Domain Name (FQDN) of each secured service. Securing the meeting server is important if you have sensitive information being exchanged in your Connect meetings. RTMP connections contain media data such as video and audio streams from your Connect meetings, as well as data from the meeting rooms such as participant names and chat text. RTMP is the protocol which the Adobe Connect meeting server uses. Securing the application server by using HTTPS is important to prevent unauthorized access of your Connect service. This includes the Connect Central administration pages for managing your Connect instance, Connect user login, and the Connect web services. HTTP is the protocol with which the Adobe Connect application server is accessed. No matter which configuration you choose, you must create DNS records for your Connect servers first. Configure software-based SSL When you configure software-based SSL, you can secure network connections to the web application server (HTTPS protocol), the meeting server (RTMPS protocol), or both. Double check the TAGs carefully again.ĥ CONFIGURE THE FOUR COMPONENTS OF CONNECT AND CQ TOGETHER ON PORT 443.

If it throws an error there has been a syntax error which is why it is not letting you open in the browser. To comment a line we use Start TAG if you see below we have just removed the closed TAG and put it at the end of first line which says Uncomment for SSL Support ) First TAG: Second TAG:- Once you uncomment the SSL required TAG s, to test if the required changes has been done successfully, please re-open the file in browser and see if you can see the same TAGs uncommented. 4 Find out the two TaG s as shown below in the file and uncomment it as shown below: (The green TAG are commented and the one on the right hand side is uncommented.

Adobe connect 9.3