Connections Desktop Plugins Password Save Policy

Created:
Author: Christoph Stoettner
Read in about 2 min · 272 words
plugins windows registry documentation

Black laptop keyboard windows key

Photo by Tadas Sar | Unsplash

During the latest automated deployment of the HCL Connections Desktop Plug-ins for Microsoft™ Windows™ , I had issues activating the Password Save Policy. We wanted to disable the option that users can save passwords.

The documentation tells us, that the registry key HKLM\SOFTWARE\Wow6432Node\IBM\Social Connectors\Settings\Password Save Policy needs to be set to 1 to achieve this.

Sadly this does not work, and I remembered, that I investigated this error already some years ago.

Setting Password Policy like the documentation describes it

The Remember the password checkbox is still active.

Administrative Template File ADM

When you install the plugins you will find two .adm files to import into the Windows Group Policy editor. For 64-bit Windows use C:\Program Files (x86)\HCL\Connections Desktop Plugins\IBMConnections64.adm, for the 32-bit version, you need to import C:\Program Files (x86)\HCL\Connections Desktop Plugins\IBMConnections64.adm. So I checked this file for 64 bit and found the registry key: HKLM\SOFTWARE\Wow6432Node\IBM\Social Connectors\Servers\Password Save Policy.

So there is an additional string Servers in the path.

229
230
231
232
233
234
235
236

; Password Save Policy
POLICY !!L_PasswordSavePolicy
   KEYNAME "SOFTWARE\Wow6432Node\IBM\Social Connectors\Servers"
   EXPLAIN !!L_PasswordSavePolicyExplain
   VALUENAME "Password Save Policy"
   VALUEON 1 
   VALUEOFF 0
END POLICY

When you set the key in the subfolder Servers it works and the password option is grayed out.

Save password grayed out, after using the path documented in ADM

Resources

Author

Christoph Stoettner

I work at Vegard IT GmbH as a senior consultant with a focus on collaboration software, Kubernetes, security and automation. I mainly deal with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform and Linux.

Sometimes my daily work results in technical talks and blog articles, which you can follow here more or less regularly. You can find the presentations in the main menu under public speaking .

I created a list of tools I use regularly, most of which have been released under an open source license.

In my spare time I read a lot, test all kinds of technical software and gadgets and try to follow about 200 RSS feeds.
Here you can find a collection of them.

This is my private blog, all opinions are my own.

           

Add a comment
Error
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

Your email address will not be published. Required fields are marked with *

Suggested Reading
Card image cap

Update Elasticsearch certificates in Componentpack

Elasticsearch in HCL Connections Componentpack is secured with Searchguard and needs certificates to work properly. These certificates are generated by bootstrap during the initial container deployment with helm.

These certificates are valid for 10 years (chain_ca.pem) or 2 years (elasticsearch*.pem) and stored in the Kubernetes secrets elasticsearch-secret, elasticsearch-7-secret. So when your HCL Connections deployment is running for 2 years, the certficates stop working.

Created: Read in about 3 min
Card image cap

Show Community Create Button only to users with role "community-creator"

Since the update to the new HCL Connections Community Card-Based Overview (Connections 6.0 CR4) I search for a way to hide the button “Create Community” from users without the role “Community-Creator”. This was always possible in the earlier versions of Connections, but the button was shown always since the update.

During the year I mostly forgot about it, but yesterday I opened a case with HCL Connections Support and got immediatly following answer:

Created:
Last Update: Read in about 2 min
Aaron Burden: Fountain pen and a notebook

Deleting temp and wstemp on Microsoft Windows Server

Since some versions of IBM Connections, it is mandatory to delete temp and wstemp of your Connections node after deployment or updates, or you end up with an old layout/design of Connections GUI.

On a Windows Server System this can be a pain, because within temp/wstemp WebSphere Application Server creates a folder structure with nodename / application server name and so on. In must cases the delete ends with the message “path too long”.

Created:
Last Update: Read in about 2 min