<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SSL termination with Share front end in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/ssl-termination-with-share-front-end/m-p/288320#M241450</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Again sorry for all the threads, this should be the last for a while.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a problem with SSL termination on an HAproxy load balancer..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I used the DevOps blog for Alfresco with HAproxy as a guide, and it partially works but with an odd behaviour.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Having a port 80 AND a port 443 front end, enables me to do any troubleshooting, and what I notice is that going straight to &lt;/SPAN&gt;&lt;A href="https://myserver/share/page/userxx/dashboard/" rel="nofollow noopener noreferrer"&gt;https://myserver/share/page/userxx/dashboard/&lt;/A&gt;&lt;SPAN&gt; works like a charm.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However is issue occurs when just using the /share URL.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When hitting up the home page using https it will reload/redirect to the http front end. We are using NTLM passthru, could it be something to do with that?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So when going to &lt;/SPAN&gt;&lt;A href="https://server/share" rel="nofollow noopener noreferrer"&gt;https://server/share&lt;/A&gt;&lt;SPAN&gt;, after authenticating, the browser reloads up the dashboard with http (not https) back at the dashboard page.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;How can SSL termination be achieved with NTLM? Is there some code in the index page on the share app thats preventing NTLM with SSL termination with HAproxy?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Like I said, going straight to &lt;/SPAN&gt;&lt;A href="https://server/share/page/userxx/dashboard" rel="nofollow noopener noreferrer"&gt;https://server/share/page/userxx/dashboard&lt;/A&gt;&lt;SPAN&gt; is wonderful, all SSL and everything is happy. The issue occurs only when going directly to the /share URL.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Im sure its something simple, but my brain is fried!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 24 Jan 2015 22:01:29 GMT</pubDate>
    <dc:creator>t16</dc:creator>
    <dc:date>2015-01-24T22:01:29Z</dc:date>
    <item>
      <title>SSL termination with Share front end</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ssl-termination-with-share-front-end/m-p/288320#M241450</link>
      <description>Hi,Again sorry for all the threads, this should be the last for a while.I have a problem with SSL termination on an HAproxy load balancer..I used the DevOps blog for Alfresco with HAproxy as a guide, and it partially works but with an odd behaviour.Having a port 80 AND a port 443 front end, enables</description>
      <pubDate>Sat, 24 Jan 2015 22:01:29 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ssl-termination-with-share-front-end/m-p/288320#M241450</guid>
      <dc:creator>t16</dc:creator>
      <dc:date>2015-01-24T22:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: SSL termination with Share front end</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ssl-termination-with-share-front-end/m-p/288321#M241451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;OK I found the answer for this if there is anyone out there wishing to to NTLM Passthru authentication, AND have SSL offload on a loadbalanced Share front end!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Since share bounces the request a few times between the browser and itself, you need to add "redirect scheme https if !{ ssl_fc }" to your HAproxy config to catch these "redirects" back to the client during NTLM auth.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No idea why it doesnt happen when going straight to the user dashboard, perhaps there is no auth required when there is a live session cookie, but visiting the /share home page will instigate an authentication regardless for best security..?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Either way, thats the solution, a happy person here!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Loving the flexibility of Alfresco, and how you can easily mess around and create your own architecture by splitting the bits off onto different servers etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The fact its so portable and you can move share around, and offload SOLR etc etc is rather amazing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Now I have SSL working on a load balanced front end share cluster, the only thing left is to bring up 2 x SOLR boxes to serve the Main repository cluster.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;GIven the fact I have SSL on the front end, and also a shared content store via NFS, any tips on what I need to do in order to get 2 x SOLR boxes speaking to the alfresco cluster via SSL?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the Keystore is on the shared content store, how does that affect both Repository servers in the cluster?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Still learning here.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Jan 2015 23:48:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ssl-termination-with-share-front-end/m-p/288321#M241451</guid>
      <dc:creator>t16</dc:creator>
      <dc:date>2015-01-24T23:48:11Z</dc:date>
    </item>
  </channel>
</rss>

