I recently worked on one integration of Sametime V 11.6 with iNotes and Verse (2.2.0). I configured everything as usual, but I still couldn’t get Sametime up and running with iNotes and Verse.
Although this has been described in the documentation, discussion forums or on various blogs, I would like to remind you once again that certain parameters need to be used.
Edit in the web.xml file in the Sametime Proxy server (sametimeproxy/conf):
Change:
antiClickJackingOption SAMEORIGIN
To:
antiClickJackingOption ALLOW-FROM
antiClickJackingUri https://*.company.com (.comapany.com = your domain)
Add the following parameters in notes.ini:
iNotes_WA_SametimeProxyLogin=1
iNotes_WA_SametimeProxy=1
INOTES_WA_SAMETIMEPROXYSERVERSSL=https://sametimeprocy.yourdomain.com:8443 (adding the port 8443 or without a port if the Sametime proxy is running on the port 443)
For Verse:
VOP_GK_SAMETIME=1
VOP_GK_SAMETIME_RICH_CLIENT=1 (optionally, if you enter 0, the Sametime web client will be used)
I added these parameters into notes.ini using a configuration document on the Domino server (Configuration / Servers / Configuration), but unfortunately still Sametime didn’t work. It was only with the help of HCL Support (Kaustubh Khismatrao) that we found out that for some reason the parameters from the configuration document were not written to notes.ini.
Yes, it’s my fault I didn’t check it out. I added the parameters directly to notes.ini and lo and behold, Sametime immediately started working.
Then an “HTTP Status 400 – Bad Request” error occurred while trying to chat in iNotes. Thanks to an article by collegue HCL Ambassador Roberto Boccadoro LINK, I solved the problem by adding two lines to the catalina.properties file in the sametimeproxy / conf directory:
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
org.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true
After restarting the Proxy server, everything worked.