Using Sametime Links(STLinks) with Mozilla Browsers.
Because of the security differences between the IE browser and Mozilla browser, there is an important step that many admins miss when setting up Sametime Links, the following is taken form the STLinks toolkit documentation.
Supporting Sametime-Enabled Pages on Separate Server with Mozilla
Mozilla JavaScript security requires that the Sametime links applet be loaded from the same host as the enabled Web page itself. This is because Mozilla security restrictions do not allow JavaScript code to communicate with an applet on a different server.
Therefore, if your Sametime-enabled pages reside on a separate application
server, you must place a copy of the Sametime links runtime files (the applet
and HTML dialog files) on your application server. In addition, Mozilla users
must use a signed version of the Sametime links applet to allow the applet to
connect to the Sametime server. The applet (stlinks.jar) is included on the
Sametime server in <SERVER Directory>\Data\domino\html\sametime\stlinks\signed.
If your HTML pages are stored on a separate application server, follow these
steps:
- Under your web server root directory, create a "sametime" folder.
- Put a copy of the “stlinks” folder from the Sametime server inside the "sametime" folder you just created.
- Replace the stlinks.jar file with the one in <SERVER Directory>\Data\domino\html\sametime\stlinks\signed.
- Make sure that the HTTP tunneling port specified in hostinfo.js matches the one used by the server. Note that if you modify the port at any time after copying the Sametime links files to the server, you must update hostinfo.js with the new port information. For more information about the HTTP tunneling port, see “Setting the HTTP Tunneling Address and Port” in Appendix A.
Note: If you want to put the files somewhere other than sametime\stlinks,
please refer to the description of setSTLinksNSCodeBase in Chapter 6.
Note The toolkit will use the Sametime links files on the application server
when using Mozilla and the Sametime links files on the Sametime server when
using Internet Explorer. Therefore, when you call SetSTLinksURL, you should
still point to the Sametime server.
| Permalink | 
Comments
Could you help me with the following issue.
I enabled sametime links in my web application. It works fine for all users in my office. But none of the users outside my office is able to login to sametime.
Our sametime server is HTTPS enabled. I tried to login as me from my home computer. I was not able to log in. So there is some difference in logging in from my office and from outside. Just not able to figure it out.
I read many articles about http tunnelling over 443 etc. Here is the message I see in the java console.
java.security.PrivilegedActionException: java.net.ConnectException: Connection refused: connect
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.net.CrossDomainXML.check(Unknown Source)
at com.sun.deploy.net.CrossDomainXML.check(Unknown Source)
at sun.plugin2.applet.Applet2SecurityManager.checkConnect(Unknown Source)
at java.net.InetAddress.getLocalHost(Unknown Source)
at com.lotus.sametime.stlinks.client.STLinksApplet.calcLocalAddress(Unknown Source)
at com.lotus.sametime.stlinks.client.STLinksApplet.access$000(Unknown Source)
at com.lotus.sametime.stlinks.client.STLinksApplet$1.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at com.sun.deploy.net.CrossDomainXML$2.run(Unknown Source)
... 8 more
network: Connecting { Link } with proxy=DIRECT
*I am not showing the hostname
Please guide me in the right direction.
Thanks,
VN.
Posted by Vijayan At 12:09:53 PM On 06/08/2009 | - Website - |