Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: Tim Conrad on 15-05-2012 01:04:09 AM Hi All, The QUAD admin guide (table B-1) it lists client connections as http (8080) or https (8443) - how do I enable https? I can't find any further reference to it in the documentation. I'm running with WebEx Social Version 2.5.2.10000.116 Thanks, Tim
Subject: RE: Client requests via https Replied by: Daniele Salladini on 15-05-2012 03:51:55 AM Https is automatically enabled on webnode, you must only tipe "https://..." in browser. D
Subject: RE: Client requests via https Replied by: duncan westlake on 15-05-2012 04:10:39 AM Hi Tim,
we were supplied the below from TAC about 8 months ago. We are on 2.5.2 as well now, we have found the IOS 2.5.2 app does not work with the solution below when using SSL.
This workaround covers the scenario when an external SSL terminator is used.
The workaround would be to add a custom properties file with the missing properties. Downside is that these changes will need to be re-applied after every upgrade.
Step 1
Create a file called custom.properties, and add the desired parameters inside it:
company.security.auth.requires.https=true
web.server.protocol=https
web.server.http.port=80
web.server.https.port=443
webdav.servlet.https.required=true
The path to that file is: /opt/cisco/WebEx Social/tomcat/webapps/ROOT/WEB-INF/classes/
Step 2
Then have the WebEx Social JVM read this property file by editing /opt/cisco/WebEx Social/tomcat/bin/setenv.sh and adding the following to the end JAVA_OPTS="${JAVA_OPTS} -Dexternal-properties=custom.properties"
where the custom.properties lies in the same folder as the portal-ext.properties.
This change has to be done on all WebEx Social nodes that need to be accessed through SSL.
Thanks
Duncan
Subject: RE: Client requests via https Replied by: Remo Peulen on 16-05-2012 11:26:07 AM Hi Duncan,
The solution you listed doesn't work because all the files you are changing are controlled by Puppet.
The HTTPS interface gets turned on by default in the latest installs of WebEx Social. Just be aware that there is no SSL certificate for this as it is not intended to be accessed directly, but only through an ACE that will be doing SSL offloading.
Thanks, Remo.
Subject: RE: Client requests via https Replied by: Tim Conrad on 16-05-2012 08:38:04 PM Also found it mentioned here
So I gather that a WebEx Social 2.5 web node is only designed to offer http, and another network appliance would be required to stand in front as the https proxy?
Subject: RE: Client requests via https Replied by: duncan westlake on 17-05-2012 04:03:02 AM Hi Tim,
Yes, that is how we are running WebEx Social. We make the changes i described above to the WebEx Social web nodes (when monit and puppet services are stopped), and are using a Riverbed Stingray load balancer as the SSL terminator / https proxy (if that is the correct way of describing it).
We have been doing so since WebEx Social 2.1. But as advised above with 2.5.2 there does seem to be an issue with the 2.5.2 IOS app when the WebEx Social Webs are configured as per my post above. All other areas work for us ok.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
