<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hcl Connections on </title>
    <link>https://stoeps.de/tags/hcl-connections/</link>
    <description>Recent content in Hcl Connections 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>&amp;copy; 2026 Christoph Stöttner - This work is licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) &lt;span class=&#39;footerimg&#39;&gt;&lt;img src=&#39;https://mirrors.creativecommons.org/presskit/icons/cc.svg&#39; alt=&#39;&#39; style=&#39;max-width: 1em;max-height:1em;margin-left: .2em;&#39;&gt;&lt;img src=&#39;https://mirrors.creativecommons.org/presskit/icons/by.svg&#39; alt=&#39;&#39; style=&#39;max-width: 1em;max-height:1em;margin-left: .2em;&#39;&gt;&lt;img src=&#39;https://mirrors.creativecommons.org/presskit/icons/sa.svg&#39; alt=&#39;&#39; style=&#39;max-width: 1em;max-height:1em;margin-left: .2em;&#39;&gt;&lt;/span&gt;</copyright>
    <lastBuildDate>Thu, 16 Oct 2025 15:00:00 +0200</lastBuildDate><atom:link href="https://stoeps.de/tags/hcl-connections/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Encrypt Customizer Traffic in HCL Connections Component Pack</title>
      <link>https://stoeps.de/posts/2025/secure_customizer_traffic/</link>
      <pubDate>Thu, 16 Oct 2025 15:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2025/secure_customizer_traffic/</guid>
      <description>&lt;div class=&#34;admonition relative overflow-hidden rounded-lg border-l-4 my-3 px-4 py-3 shadow-sm&#34; data-type=&#34;warning&#34;&gt;&#xA;      &lt;div class=&#34;flex items-center gap-2 font-semibold text-inherit&#34;&gt;&#xA;        &lt;div class=&#34;flex shrink-0 h-5 w-5 items-center justify-center text-lg&#34;&gt;&lt;span class=&#34;relative block icon&#34;&gt;&lt;svg xmlns=&#34;http://www.w3.org/2000/svg&#34; viewBox=&#34;0 0 512 512&#34;&gt;&lt;path fill=&#34;currentColor&#34; d=&#34;M506.3 417l-213.3-364c-16.33-28-57.54-28-73.98 0l-213.2 364C-10.59 444.9 9.849 480 42.74 480h426.6C502.1 480 522.6 445 506.3 417zM232 168c0-13.25 10.75-24 24-24S280 154.8 280 168v128c0 13.25-10.75 24-23.1 24S232 309.3 232 296V168zM256 416c-17.36 0-31.44-14.08-31.44-31.44c0-17.36 14.07-31.44 31.44-31.44s31.44 14.08 31.44 31.44C287.4 401.9 273.4 416 256 416z&#34;/&gt;&lt;/svg&gt;&#xA;&lt;/span&gt;&lt;/div&gt;&#xA;        &lt;div class=&#34;grow&#34;&gt;&#xA;          Warning&#xA;        &lt;/div&gt;&#xA;      &lt;/div&gt;&lt;div class=&#34;admonition-content mt-3 text-base leading-relaxed text-inherit&#34;&gt;&lt;p&gt;The is just a proof of concept and shouldn&amp;rsquo;t be used in production! I still have some issues with redirects to the new hostname.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;In the series of encrypting network traffic within HCL Connections and Component Pack:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://stoeps.de/posts/2025/encrypt_ihs_proxypass_to_cp/&#34; &gt;Encrypt IHS Proxypass Traffic To Component Pack&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://stoeps.de/posts/2025/securing_redis_traffic_in_hcl_connections/&#34; &gt;Securing Redis Traffic in HCL Connections with SSH Tunnels&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;the customizer part is missing. In a default configuration (or when you install as documented), the traffic from IHS and NGINX that is forwarded to the customizer (mw-proxy) and Ingress is unencrypted.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2025/secure_customizer_traffic/feature.jpg" />
    </item>
    
    <item>
      <title>Encrypt IHS proxypass traffic to Component Pack</title>
      <link>https://stoeps.de/posts/2025/encrypt_ihs_proxypass_to_cp/</link>
      <pubDate>Fri, 23 May 2025 21:30:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2025/encrypt_ihs_proxypass_to_cp/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m still working on encrypting all network traffic between Connections and Component Pack servers. This time I checked the &lt;a href=&#34;https://kubernetes.github.io/ingress-nginx/user-guide/tls/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Ingress-Nginx Controller - TLS/HTTPS&lt;/a&gt; documentation.&lt;/p&gt;&#xA;&lt;p&gt;The default configuration for connecting IHS with Component Pack uses the plain HTTP port 32080. All traffic like &lt;code&gt;/social&lt;/code&gt; or the Tailored Experience wizard is routed from IHS to Kubernetes on port 32080.&lt;/p&gt;&#xA;&lt;p&gt;Our target is to encrypt the traffic on port 32443.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2025/encrypt_ihs_proxypass_to_cp/feature.jpg" />
    </item>
    
    <item>
      <title>Securing Redis Traffic in HCL Connections with SSH Tunnels</title>
      <link>https://stoeps.de/posts/2025/securing_redis_traffic_in_hcl_connections/</link>
      <pubDate>Mon, 05 May 2025 22:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2025/securing_redis_traffic_in_hcl_connections/</guid>
      <description>&lt;p&gt;At the moment I&amp;rsquo;m working with a customer to secure all traffic in HCL Connections. The target is to have only encrypted network traffic between servers.&lt;/p&gt;&#xA;&lt;p&gt;Today I started enabling encryption to Redis. This is a &lt;a href=&#34;https://help.hcl-software.com/connections/v8/admin/install/cp_config_om_redis_secure_linux.html&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;documented process&lt;/a&gt;, but the documentation is outdated and incomplete.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2025/securing_redis_traffic_in_hcl_connections/feature.jpg" />
    </item>
    
    <item>
      <title>Embed a video into Wikis or Blogs</title>
      <link>https://stoeps.de/posts/2025/embedded_videos_in_connections/</link>
      <pubDate>Wed, 30 Apr 2025 22:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2025/embedded_videos_in_connections/</guid>
      <description>&lt;p&gt;Today I read the article &lt;a href=&#34;https://support.hcl-software.com/csm?id=kb_article&amp;amp;sysparm_article=KB0118248&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;KB0118248&lt;/a&gt; and remembered my &lt;a href=&#34;https://stoeps.de/posts/2018/2018-02-05-embed-uploaded-videos-to-ibm-connections-blog-post-or-wiki-page/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;blog post from 2018&lt;/a&gt;. I also checked the attached &lt;a href=&#34;https://connections-ideas.hcltechsw.com/ideas/IDEACNCTNS-I-2499&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;aha idea&lt;/a&gt; where a comment states that you can use iframe for Youtube. &lt;strong&gt;Despite what KB0118248 incorrectly states, it is absolutely possible to embed videos in HCL Connections blogs and wikis using the HTML video tag as demonstrated in this post.&lt;/strong&gt;&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2025/embedded_videos_in_connections/feature.jpg" />
    </item>
    
    <item>
      <title>Configure Kerberos / SPNEGO with Connections</title>
      <link>https://stoeps.de/posts/2025/kerberos_single_sign/</link>
      <pubDate>Sat, 26 Apr 2025 22:00:00 +0200</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2025/kerberos_single_sign/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://help.hcl-software.com/connections/v7/admin/secure/t_install_kerb_setup_spnego.html&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;HCL Connections documentation&lt;/a&gt; describes the process for configuring Windows desktop single-sign-on in a somewhat complicated way.&#xA;Here are the necessary steps for setting up with the highest possible encryption.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://stoeps.de/posts/2025/kerberos_single_sign/feature.jpg" />
    </item>
    
  </channel>
</rss>
