Cisco Cisco WebEx Social for Mobile

The master account feature, which you configure from the Portal drawer, lets Cisco WebEx Social 
users set the same login credentials (user name and password) that they use to access various 
services in Cisco WebEx Social.

The session setting feature, which you access from the Server drawer, lets you configure the 
maximum number of times that any user can be logged in to Cisco WebEx Social concurrently.

Email configuration items have been consolidated in the Email Configuration area in the 
Application > Integration page of the Director.

This section describes limitation, restrictions, and other important information that applies to this release 
of Cisco WebEx Social.

Although the CAS tab appears in the Account Settings > Portal > Settings > Authentication window, 
Cisco WebEx Social does not support Central Authentication Service (CAS) and the fields in this 
tab are not used.

When using Show & Share release 5.3 with Cisco WebEx Social, do not install Show & Share 
patch1.

If SSO is enabled in your network, make sure that the Enable SSO box in the Notifier area of the 
Configuration window in the Director is checked. This configuration ensures that user accounts are 
not locked if a password lockout policy is configured in your Active Directory.

Cisco WebEx Social no longer required redirects in the Cisco WebEx Social Apache server to the 
Sametime Proxy server. For Sametime chat to be operational, this change requires that each Cisco 
WebEx Social client (browser or mobile application that loading Cisco WebEx Social) have routing 
access to the SameTime proxy server.

Using the ext3 file system on your NFS server can limit the number of library documents and post 
attachments that Cisco WebEx Social can store. For more information, use the Bug Toolkit to access 
the defect number CSCtk55146 (see the 

).

This Cisco WebEx Social release adds support for using the IBM Sametime Connect client for chat 
and availability in place of the integrated Cisco WebEx Social client. To determine the availability 
of Sametime and to launch the client on new chat sessions, Cisco WebEx Social sends HTTP 
requests to the local Sametime service at localhost port 59449. Because the local Sametime service 
supports only HTTP, if your organization accesses Cisco WebEx Social through HTTPS, the web 
browsers of your users may block outgoing HTTP requests as a security measure. To allow Cisco 
WebEx Social to launch Sametime, you must instruct users to enable mixed content. Enabling mixed 
content varies from browser to browser. See your web browser documentation or search the Internet 
for detailed steps.

http://www.cisco.com/en/US/products/ps10668/tsd_products_support_series_home.html

.