HCL Sametime 11.6 and MongoDB 4.4 - how to enable mongo security correctly

HCL Sametime 11.6 is supporting MongoDB 4.4 and this is the suggested version in case of new install.

One of the suggested steps during a Community setup is enable the Mongo security as described here , but the steps there are not enough, because 4.4 version in case of replica set , require also the creation and the use of a shared key to every Mongo server involved in the replica set, even if the replica set is composed by 1 node.

The first step required is the creation of  the authentication key that I made with the following command:

openssl rand -base64 741 > /etc/mongod.key

After the creation of the key, ownership and permission should be set in the right way:

chmod 600 /etc/mongod.key

chown mongod: /etc/mongod.key

now it's possible to enable the security  inside /etc/mongod.conf

security:

  authorization: enabled

  keyFile: /etc/mongod.key

How to install correctly Sametime Community over Domino 11.0.1 FP3 on linux

 During last weeks I'm working mostly on HCL Sametime preparing some meetings environments.

After the release of the 11.6 we have noted the server wasn't able to start if installed after FP3 of Domino 11.0.1.

The issue is similar to the Traveler issue , but we have fixed it in this way:

1. Domino 11.0.1 install
2. Fp3 install
3. Rename 2 libraries inside /opt/hcl/domino/notes/latest/linux 
4. mv OLDlibcrypto.so.1.1 libcrypto.so.1.1 
5. mv OLDlibssl.so.1.1 libssl.so.1.1
6. Install Community 11.6

You could find the related technote here made by the HCL support here

LetsConnect webinar - HCL Connections v8 Roadmap and first look

During the  last LetsConnect webinar,  Adam Gartenberg from HCL has run an interesting sessions showing the first look of some of the new features of Connections v8 like new universal search, new UI or the new universal upload button.

This release of Connections v8 is planned to be released during Q4 2021

LetsConnect May webinar : How to get most of your Connections Deployment and see the Connections Roadmap

 Tomorrow May 11 3pm CET there will be the LetsConnect May webinar , with the following agenda :

- HCL Connections News
Hear the latest news and thoughts about HCL Connections

- Fine-tune HCL Connections to your needs
Once you finish installation of HCL Connections, there are dozens of features you can enable or disable in so called post-installation steps. Unfortunately many of the useful features are not enabled by default and therefore missed by many admins to the detriment of users. In this session we will walk through most of the features and advice how to make Connections users engaged and happy.

- HCL Connections Roadmap presented by HCL
With the most recent release of HCL Connections out the door, we are working hard on the next release. In this session we will share a preview of how the next Connections release creates a new experience that will let users enjoy fluid collaboration within Connections and beyond.

Don't miss the opportunity to be informed about last news, tips and roadmap of your preferred ESN !

To reserve your free seat , please go to this link and place your registration !

HCL Connections 7.0 - cumulative fix CFix.7.0.2105 released

HCL has released a new big, cumulative fix named CFix.7.0.2105 . This new cumulative fix include the previous cumulative fix released last Feb , and cloud be installed on Cnx GA or with that cf installed.

Here at this page you could find the list of the corrections included.

The only requirement for this fix is to use the updated update installer  HCL Connections V7.0 Update Wizard (2104)

HCL Connections - how fix bad request error when login with Spnego SSO enabled

One of my HCL Customers has reported the following error

Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

when some users was trying to login. 

Connections was not loaded at all, and the HTTP error appeared.
After some investigations we have set this setting on the IBM HTTP server:

LimitRequestFieldSize 12288

in some case , with Spnego SSO enabled a very large cookie could be generated and the default value of this setting ( 8190 bytes ) could not be enough to guarantee the login.

If you like to know more about this , please read the following IBM Technotes:

• Request Header Field Size Exceeds Limit for Web server
• Increasing or decreasing the size of the HTTP Request header field for IBM HTTP Server

HCL Connections & Microsoft 365 - new integration video

Some days ago HCL has run an interesting webinar about integrations between HCL Connections and Microsoft 365. 

If you are interested to about how  Connections could perfectly work with that service, please check the video below !