Adobe Connect ACTS – Switch the Default ACTS Service protocol from WS to WSS

Objective :

How to switch the default ACTS connection from WS to WSS on an already installed ACTS service. WS is the by default option of installation and WSS is the more secure option.

So if you have ACTS component already installed on an environment with the default non-secure WS protocol, and you would like to switch to apply SSL now on the ACTS service, below described steps should be able to help here and this method may save you from actually going through a reinstall of the service itself.

Environment :

Adobe Connect On-premise
Adobe Connect version 10.1
Adobe Connect Transmuxing Service

Solution :

Follow the following steps :-

• Goto the Adobe Connect server(not the ACTS server)
• Open connect\customi.ini file for editing
• Add this parameter to the very end of the file

ACTS_PROTOCOL=wss:443

• Make sure the Adobe Connect server can resolve the machine-name of the ACTS server. A hosts file may be required for this.
• Make sure the ACTS server can resolve the external name of the AMS Meeting server.
• Restart all the Adobe Connect services on the Connect server
• Restart the ACTS service on the ACTS server

Here is a graphical demonstration of the cluster connection workflow including ACTS service :

Workflow Diagram – II

Sample Stunnel.conf

; Protocol version (all, SSLv2, SSLv3, TLSv1)
sslVersion = all
options = NO_SSLv2
options = NO_SSLv3
fips = no


; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
TIMEOUTclose=0
options = DONT_INSERT_EMPTY_FRAGMENTS

[acts]
; accept = ACTS IP:443
accept = 10.1.1.3:443

; When stunnel is on the same box, simply leave the below IP address as 127.0.0.1
connect = 127.0.0.1:9002

; Certificate information for Connect Meetings.
; This assumes you put the cert and key in the root folder of stunnel
;cert = CertificateNameHere.pem
;key = CerificateKeyNameHere.pem
cert = C:\Connect\stunnel\certs\public_certificate_acts-server.pem
key = C:\Connect\stunnel\certs\private_key_meeting-server.key.pem
; ciphers = ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH
ciphers = ALL:!AECDH:!ADH:!LOW:!EXP:!MD5:@STRENGTH 

Additional Information :

As a best practice, it would be useful to exit all open browsers and start a fresh one for testing HTML client fresh after the above changes have been added.