22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

12.2.2 Proxy support for Sametime clients<br />

544 Lotus Security Handbook<br />

Table 12-1 shows the proxy types through which clients can connect to the<br />

server.<br />

Table 12-1 Connection proxy types<br />

Sametime client SOCKS 4 proxy SOCKS 5 proxy HTTP proxy HTTPS proxy<br />

Connect Supported Supported Supported Supported<br />

Meeting Room screen<br />

sharing and whiteboard<br />

components<br />

Meeting Room participant<br />

list and chat components<br />

Meeting room interactive<br />

audio and video<br />

components<br />

Supported Not supported Supported Not supported<br />

(see following<br />

note)<br />

Supported Not supported Supported Not supported<br />

Supported Not supported Not supported Not supported<br />

Broadcast Supported Not supported Supported Not supported<br />

Presence list components<br />

in Sametime discussion<br />

and teamroom databases<br />

Supported Not supported Supported Not supported<br />

Note: It is important to understand that the Sametime Meeting Room clients<br />

can make HTTP connections through an HTTPS proxy. However, Sametime<br />

Meeting Room clients cannot make HTTPS connections through the HTTPS<br />

proxy. Sametime Connect supports a special feature of HTTPS proxies (called<br />

CONNECT) that enables the Sametime Connect client to maintain a<br />

persistent, asynchronous connection through an HTTPS proxy. The Meeting<br />

Room client does not support this “CONNECT” feature of HTTPS proxies, so<br />

cannot maintain an HTTPS connection through an HTTPS proxy.<br />

12.2.3 Securing the Sametime Java connect client<br />

Authentication<br />

SSL can be used to encrypt the initial connection between a Web browser and<br />

the Sametime server. This use of SSL will encrypt the HTTP handshake that<br />

initiates the authentication.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!