Change the hostname in url in invitation email

[rhannink]

Hello,

Whenever I invite an external user from Alfresc Share, it sends an email containing an accept and reject link. Both links however have the intranet hostname http://share:8080 as hostname. While I would like this to be the FQD http://share.domain.nl:8080 so external users can directly use this link.

I saw that the invitation mail uses the url from the inviters browser so if my internal users send the invitation while their browser points at share.domainname.nl everything is ok.

Can I overwrite this setting in Alfresco so it always uses the FQD in the url in the invitation emails independent of the browsers url to Alfresco.

Thanks in advance,

Remco

[x1m]

To fix this you have to edit the alfresco-global.properties file

In this case we use SSL encryption using the standard port 443 for HTTPS. This also fix the problem showing the images in the e-mail.


Locate and edit the following configuration file:
../tomcat/shared/classes/alfresco-global.properties

Change:
share.context=share
share.host=127.0.0.1
share.port=8080
share.protocol=http

To:
share.context=share
share.host=www.myalfresco.com
share.port=443
share.protocol=https

[devodl]

I was stymied by the same and/or related problem:  URL embedded in email notifications (not invitation)
The line in the email template that generates the link in email notifications looks like this:

${url.serverPath}/share/page/site/${site}/document-details?nodeRef=${document.nodeRef}‍

Environment
Alfresco community 4.0.c
Share webapp server is separate (Tomcat and Host) from the Alfresco repository server
As one posting states the email is generated by the repository server, not the Share webapp so my focus was on the Alfresco repository server. Changing the following  {repositoryServer}/tomcat/share/classes/alfresco-global.properties 

alfresco.context=alfresco
alfresco.host=mycompany.com
alfresco.port=80
alfresco.protocol=http

share.context=share
share.host=mycompany.com
share.port=80
share.protocol=http
‍‍‍‍‍‍‍‍‍‍

Had no effect whatsoever on ${url.serverPath}

Solution
Adding the a new property to {repositoryServer}/tomcat/share/classes/alfresco-global.properties 
# Repository endpoint - used by Activity Service - apparently deprecated but still used
repo.remote.url=http://mycompany.com
# Example settings from deprecated "repository.properties"
#repo.remote.url=http://mycompany.com:8080/alfresco
#repo.remote.endpoint=/service
and then restarting the repository server was the solution.
This property is documented here: https://issues.alfresco.com/jira/browse/ALF-10713

Note: The repo.remote.url I specified has no context (/share) because the context is specified in the email template.
I am not sure if this breaks anything else but it solved my problem.

I hope someone finds this posting useful.

Steve

[digihorse]

Steve,
   Yup. That was the final piece. However, it required all of the entries in the alfresco-global.properties, not just he remote URL one.  Would be nice if this were documented somewhere sane.

[fred-xte]

The documentation below tells us WHAT to do, but not HOW to do it. What config file needs to be edited, or what admin page contains the form for defining and creating the publicly addressable URL?

http://docs.alfresco.com/3.5/index.jsp?topic=%2Fcom.alfresco.team.doc%2Ftasks%2Fat-install-linux.htm...

This URL is relevant only when you are working on the machine on which Alfresco Team is installed. However, other users will not be able to access this URL from their machines. To give other users access to the machine where Alfresco Team is installed, you need to define and create a publicly addressable name.

   1.  Disconnect from the URL http://127.0.0.1:8080/share.
   2. Define a name for the server and create the publicly addressable name. This is a name that you will need to publicize to the Alfresco Team members.
    3. Test the publicly addressable URL from a different machine. Use the addressable name, replacing the 127.0.0.1 in the URL, for example, http://<your-server-name>:8080/share.

saunan, you are right. The documentation do not clearly show HOW to do it.

Anybody have an idea ?
Thanks in advance.