topic Re: Share published but not Alfresco in Alfresco Archive

Share published but not Alfresco

pitacsk8 — Thu, 13 Feb 2014 18:14:57 GMT

I want to deploy Alfresco (explorer) and Share on the same server with the same Tomcat with HTTPS via AJP using Apache ProxyPass.But I only want to publish on the Internet the URL of Share. So the URL arepublic) https://www.myshare.com/share(internal) https://internalServerName/alfrescoBut a very

Re: Share published but not Alfresco

cristinamr — Sat, 01 Mar 2014 15:43:11 GMT

Hey pitacsk8, did you get the solution for this issue?

Cheers,

Cristina.

Re: Share published but not Alfresco

pitacsk8 — Sat, 01 Mar 2014 16:56:30 GMT

I've been working a lot on this problem, but I couldn't fix it. Currently, I've to choose between publish both or neither.

Please, can anybody help us? Any track?

Re: Share published but not Alfresco

cristinamr — Sat, 01 Mar 2014 21:43:00 GMT

I will try to help you. Well, in one client I had the same situation, in my case we did the following configuration and works:

On alfresco-global.properties


alfresco.context=alfresco
alfresco.host=internal.url
alfresco.port=1234
alfresco.protocol=http

share.context=share
share.host=external.url
share.port=80
share.protocol=http
‍‍‍‍‍‍‍‍‍‍‍

ON my share-config-custom.xml


<config evaluator="string-compare" condition="Remote">
      <remote>
         <endpoint>
            <id>alfresco-noauth</id>
            <name>Alfresco - unauthenticated access</name>
            <description>Access to Alfresco Repository WebScripts that do not require authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://internal.url:1234/alfresco/s</endpoint-url>
            <identity>none</identity>
         </endpoint>

         <endpoint>
            <id>alfresco</id>
            <name>Alfresco - user access</name>
            <description>Access to Alfresco Repository WebScripts that require user authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://internal.url:1234/alfresco/s</endpoint-url>
            <identity>user</identity>
         </endpoint>

         <endpoint>
            <id>alfresco-feed</id>
            <name>Alfresco Feed</name>
            <description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>
            <connector-id>http</connector-id>
            <endpoint-url>http://internal.url:1234/alfresco/s</endpoint-url>
            <basic-auth>true</basic-auth>
            <identity>user</identity>
         </endpoint>
      </remote>
   </config>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Well, in our case we detected that sometimes instead to load /share, it was forcing to load /alfresco and for that issue we did this in the ftls:


 <a href="${url.context?replace("alfresco","share")}/page/result-details?nodeRef=${nodeResult.nodeRef?string}"  target="result">${nodeResult.properties["cm:title"]?string}</a>
‍‍‍

We haven´t anything more configure.. Can you check your config and tell me if it´s persisting your problem?

Cheers,

Cris.

Re: Share published but not Alfresco

pitacsk8 — Mon, 03 Mar 2014 08:46:43 GMT

Thank you for your reply CristinaMR. The configuration seems to be de same. But I hadn't thought of modifying the ftls. Have you modify all the ftls of Share?

Re: Share published but not Alfresco

cristinamr — Mon, 03 Mar 2014 21:41:58 GMT

pitacsk8: Nop. We detected some FTLs of Share, when we call them, instead to have Share´s context got the Alfresco´s context, for that reason we did this change.
But in general, I think that you´re behaviour is strange. Give me some time and I will ask to one college (I hope that we can help you).

Cris.

Re: Share published but not Alfresco

pitacsk8 — Tue, 04 Mar 2014 09:00:25 GMT

Thanks CristinaMR, I hope that someone can help me

Re: Share published but not Alfresco

cristinamr — Tue, 04 Mar 2014 10:19:25 GMT

pitacsk8, try this:

1. Rename your share-config-custom.xml to share-config-custom.xml.original
2. Create a new xml call share-config-custom.xml and paste this config with your configuration (internal.url and port):


<config evaluator="string-compare" condition="Remote">
      <remote>
         <endpoint>
            <id>alfresco-noauth</id>
            <name>Alfresco - unauthenticated access</name>
            <description>Access to Alfresco Repository WebScripts that do not require authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://internal.url:PORT/alfresco/s</endpoint-url>
            <identity>none</identity>
         </endpoint>
 
         <endpoint>
            <id>alfresco</id>
            <name>Alfresco - user access</name>
            <description>Access to Alfresco Repository WebScripts that require user authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://internal.url:PORT/alfresco/s</endpoint-url>
            <identity>user</identity>
         </endpoint>
 
         <endpoint>
            <id>alfresco-feed</id>
            <name>Alfresco Feed</name>
            <description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>
            <connector-id>http</connector-id>
            <endpoint-url>http://internal.url:PORT/alfresco/s</endpoint-url>
            <basic-auth>true</basic-auth>
            <identity>user</identity>
         </endpoint>
      </remote>
   </config>
 ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

3. Restart and try it

Re: Share published but not Alfresco

cybermakoki — Tue, 04 Mar 2014 14:17:41 GMT

Hi pitacsk8,

Besides what CristinaMR says, I think that you can use the default configuration of share-config-custom.xml (with localhost) and configure your alfresco-global.properties like this:


alfresco.context=alfresco
alfresco.host=www.myshare.com
alfresco.port=443
alfresco.protocol=https
share.context=share
share.host=www.myshare.com
share.port=443
share.protocol=https
‍‍‍‍‍‍‍‍‍‍

and then, in your apache configuration, only configure access for share with something similar to this:


<VirtualHost *:80>
    ServerName www.myshare.com

    […]
   
    RewriteEngine On
    RewriteRule ^/$ share [R]

    ProxyPass /share ajp://localhost:8009/share
    ProxyPassReverse  /share  ajp://localhost:8009/share

</VirtualHost>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Share published but not Alfresco

cristinamr — Tue, 04 Mar 2014 14:23:35 GMT

I'm agree with cybermakoki: Try this too and close your fingers!

Re: Share published but not Alfresco

cristinamr — Fri, 07 Mar 2014 19:36:02 GMT

Any news pitacsk8?