<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Documentation on </title>
    <link>https://stoeps.de/tags/documentation/</link>
    <description>Recent content in Documentation on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>christoph.stoettner@stoeps.de (Christoph Stoettner)</managingEditor>
    <webMaster>christoph.stoettner@stoeps.de (Christoph Stoettner)</webMaster>
    <copyright>© 2026 Christoph Stoettner</copyright>
    <lastBuildDate>Fri, 02 Sep 2022 13:00:00 +0200</lastBuildDate><atom:link href="https://stoeps.de/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Update Elasticsearch certificates in Componentpack</title>
      <link>https://stoeps.de/posts/2022/update-elasticsearch-certificates/</link>
      <pubDate>Fri, 02 Sep 2022 13:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2022/update-elasticsearch-certificates/</guid>
      <description>&lt;p&gt;Elasticsearch in HCL Connections Componentpack is secured with Searchguard and needs certificates to work properly. These certificates are generated by &lt;a href=&#34;https://help.hcltechsw.com/connections/v7/admin/install/cp_install_services_tasks.html?hl=bootstrap#cp_install_services_tasks__section_iqb_24c_qmb&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;bootstrap&lt;/a&gt; during the initial container deployment with &lt;code&gt;helm&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;These certificates are valid for 10 years (&lt;code&gt;chain_ca.pem&lt;/code&gt;) or 2 years (&lt;code&gt;elasticsearch*.pem&lt;/code&gt;) and stored in the Kubernetes secrets &lt;code&gt;elasticsearch-secret&lt;/code&gt;, &lt;code&gt;elasticsearch-7-secret&lt;/code&gt;. So when your HCL Connections deployment is running for 2 years, the certficates stop working.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2022/update-elasticsearch-certificates/feature.jpg" />
    </item>
    
    <item>
      <title>Connections Desktop Plugins Password Save Policy</title>
      <link>https://stoeps.de/posts/2021/connections_desktop_plugins_password_save_policy/</link>
      <pubDate>Mon, 06 Dec 2021 10:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2021/connections_desktop_plugins_password_save_policy/</guid>
      <description>&lt;p&gt;During the latest automated deployment of the &lt;a href=&#34;https://help.hcltechsw.com/connections/v7/connectors/enduser/c_files_window_install_ovr.html&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;HCL Connections Desktop Plug-ins for Microsoft™ Windows™&lt;/a&gt;, I had issues activating the &lt;code&gt;Password Save Policy&lt;/code&gt;. We wanted to disable the option that users can save passwords.&lt;/p&gt;&#xA;&lt;p&gt;The documentation tells us, that the registry key &lt;code&gt;HKLM\SOFTWARE\Wow6432Node\IBM\Social Connectors\Settings\Password Save Policy&lt;/code&gt; needs to be set to &lt;code&gt;1&lt;/code&gt; to achieve this.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2021/connections_desktop_plugins_password_save_policy/feature.jpg" />
    </item>
    
    <item>
      <title>Show Community Create Button only to users with role &#34;community-creator&#34;</title>
      <link>https://stoeps.de/posts/2020/community_create_button/</link>
      <pubDate>Thu, 17 Dec 2020 09:05:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2020/community_create_button/</guid>
      <description>&lt;p&gt;Since the update to the new &lt;a href=&#34;https://help.hcltechsw.com/connections/v6/user/communities/t_com_search.html&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;HCL Connections Community Card-Based Overview (Connections 6.0 CR4)&lt;/a&gt; I search for a way to hide the button &amp;ldquo;Create Community&amp;rdquo; from users without the role &amp;ldquo;Community-Creator&amp;rdquo;.&#xA;This was always possible in the earlier versions of Connections, but the button was shown always since the update.&lt;/p&gt;&#xA;&lt;p&gt;During the year I mostly forgot about it, but yesterday I opened a case with HCL Connections Support and got immediatly following answer:&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2020/community_create_button/feature.jpg" />
    </item>
    
    <item>
      <title>Create a printable and portable Connections Product Documentation</title>
      <link>https://stoeps.de/posts/2013/2013-07-15-create-a-printable-and-portable-connections-product-docu/</link>
      <pubDate>Mon, 15 Jul 2013 20:22:01 +0000</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2013/2013-07-15-create-a-printable-and-portable-connections-product-docu/</guid>
      <description></description>
      
    </item>
    
  </channel>
</rss>
