Photos missing in Sametime Webclient

Recently I tried to configure Sametime Proxy Server to show profile photos from IBM Connections in Sametime web client business cards. SSO through LTPA was setup between Sametime, 9.0.1 version, and Connections, 5.5 CR2 version, environment and the configuration needed was done on the Sametime Proxy server. But after synchronization and restart of the ST Proxy, the photos would still not show up in the web client.

Video showing this error.

As you can see the browser just tries to load the photo and there are no errors in GUI. With Chrome and Fiddler I managed to catch HTTP 403 error, I could also see the HTTP 403 error in the IBM HTTP Server log, rather than that there were no other errors. I think it is also important to mention that with IE and Fiddler I could not catch the HTTP 403 error, the IE would not even stop trying to load the photo.

The solution was to set “allowJsonpJavelin” to “true” in the “profiles-config.xml” file.

<allowJsonpJavelin enabled=”true”/> 
After that just synchronize the nodes and restart Connections Applications, most likely it will be enough just to restart the “Profiles” application.
Big thanks to Martin Leyrer and Dave Fleetham for helping me solve this one, I hope this will show up soon in the Knowledge Center. 🙂
This configuration change is needed only if you upgrade Connections to 5.0 CR4 or later.
There is also a blog post from Tom Bosmans about this matter.

 

Advertisements

IBM Notes Traveler 9.0.1.16 Available

IBM Notes Traveler 9.0.1.16 Update is available for Download.

This update covers all previous updates and beside usual fixes, this updates enables Java 1.8 Support. Which is important and makes this update a requirement before installing IBM Domino Feature Pack 8 which will come later on.

Fix List

Release Notes

Download from Fix Central

Make sure to visit Daniel Nashed´s Blog, specifically the posts about IBM Domino 9.0.1 Feature Pack 8 and Java 1.8 Support where he described the impact of the coming changes and new features in great detail.

Certificate Error while integrating iNotes with Connections Files and Docs

I have recently integrated iNotes with Connections Files and Docs in an environment where Windows CA is being used.

After the configuration was completed there were the following errors in the iNotes GUI:

Domino Release 9.0.1FP7 HF409 (Windows/64)

$HaikuForm – 901FP7INHF90

Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

02/01/2017 09:06:11AM The supported IBM Docs file types cannot be retrieved due to an IBM Docs server error: 500

02/01/2017 09:06:11AM Error encountered retrieving data: Unable to connect to your Web server. Please retry your action at a later time.

02/01/2017 09:08:59AM status=500: { “error”: {“@code”:”1000″,”param” : [ {“@name”:”exception”,”value” : “javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: 3659″} ],”details” : “”}}

02/01/2017 09:09:25AM A problem has occurred which may have caused the current operation to fail.

The Domino Console was showing the following:

[11D8:000A-1F48] 01.02.2017 08:56:13 HTTP JVM: java.security.cert.CertificateException: 3659. For more detailed information, please consult error-log-0.xml located in E:/IBM/Domino/Data/domino/workspace/logs

The same error was logged in the “error-log-0.log” file.

The solution for this issue was to import the CA Certificate into the “cacerts” java security file on the Domino server. For this I used the ikeyman utility, you can also use “kyrtool” if you are familiar with it, just make sure you have a backup of the “cacerts” file if something goes wrong.

The “cacerts” file is located under: “<domino_installation_directory>\jvm\lib\security”.

“ikeyman” can be found in “<domino_installation_directory>\jvm\bin”.

Just start the “ikeyman” utility as an Administrator and open the “cacerts” java file.

Default PW of the “cacerts” file is “changeit”.

Click OK, and enter a new alias name for the certificate.

After that I just restarted the Domino server and the problem was solved.