Problem editing in MS Office

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Member II

Problem editing in MS Office

Hi
I'm having and issue with the settings in alfresco-global.properties not sticking. I'm running gui81-alfresco1 in Docker on a Synology NAS and I'm trying to get it so that when I view a document I can click "Edit in Microfot Office". However, when I click it, I get and error saying it can't connect to 127.0.0.1 (or something like that
So I tried editing alfresco-global.properties to the server local IP address. E.g.,

dir.root=/alfresco/alf_data

alfresco.context=alfresco
alfresco.host=127.0.0.1
alfresco.port=8080
alfresco.protocol=http

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

Change to

dir.root=/alfresco/alf_data

alfresco.context=alfresco
alfresco.host=192.168.100.10
alfresco.port=8080
alfresco.protocol=http

share.context=share
share.host=192.168.100.10
share.port=8080
share.protocol=http

save and quit bash,
If I re-open the file in vi I can still see the changes but if I restart the Docker alfresco-global.properties reverts back to the default.
Is there something I'm doing wrong?

Spoiler
 
1 Reply
Highlighted
Master

Re: Problem editing in MS Office

I am not sure what "gui81-alfresco1" is supposed to be. Is it the name of the Docker container or the image? If it is an image, who provided / built it (using what base)?

Generally I would assume that by restarting your Docker instance, the alfresco-global.properties simply resets to the default state of the image. This would happen e.g. if you used the default Alfresco Docker images and completely stopped + removed a running container instance, and then restarted. In the default images, this is by design, and you are supposed to provide custom parameters via environment variables passed to the Docker container, typically using the JAVA_OPTS parameter with addition of various -D Java system properties flags.

Also, it is generally not recommended to use IP-based addresses for complex functionality like editing in MS Office. Windows / Office have various security mechanisms in place which typically expect / require a proper FQDN to be present, otherwise they can potentially limit some functionalities for security reasons. As such, you should try to give your Alfresco instance a proper domain name entry, e.g. alfresco.acme.com, and better yet, set up a proper reverse proxy with SSL termination, so Windows / Office may even support potentially insecure authentication methods, like HTTP BASIC.