Onlyoffice Alfresco connector

[joakim.djuvfelt]

Hello,

We are trying to install the OnlyOffice connector for Alfresco.
Alfresco version: 5.2.g
Connector version: 6.1.0

The installation seems to work, however editing documents does not work.
We observe no errors in the alfresco logs.

Errors observed on the document server:

open() “/var/www/onlyoffice/documentserver-example/welcome/sito/wp-includes/wlwmanifest.xml” failed (2: No such file or directory), client: client-ip, server: , request: “GET /welcome//sito/wp-includes/wlwmanifest.xml HTTP/1.1”, host: “alfresco-host”

ERROR] [localhost] [aa8c9a2d-d5ca-4def-9b0f-570c8b408456_1.1] [Administrator1] nodeJS - postData error: url = https://(alfresco-host)/alfresco/s/parashift/onlyoffice/callback?nodeRef=workspace://SpacesStore/aa8c9a2d-d5ca…

Is there any specific configurations we have missed?

Br,
Joakim

[Nikolas]

Hi @joakim.djuvfelt
Please provide some additional information about:

1. Please point us to ONLYOFFICE and Alfresco integration guides which you used.
2. Could you please specify, when this issue started? Was there any operation which, after, this issue appeared?
3. Does the Document Server work in front of a proxy server?
4. Please attach the contents of /etc/only office/documentserver/local.json and screenshot connector settings. (hide sensitive information)
5. Is the document server connection on the connector settings page successful?

[joakim.djuvfelt]

Hello,

Sorry for the delayed answer.

The guides used:
For docserver: Installing ONLYOFFICE Docs for Debian, Ubuntu, and derivatives - ONLYOFFICE
For Alfresco: ONLYOFFICE Api Documentation - ONLYOFFICE Alfresco module package

We have not managed to get it to work at all yet, so this occured during the installation unfortunately.

The Document Server is setup with a nginx proxy on the same server.

local.json:

We think the connection is successful, after adding the secret in alfresco-global.properties we got a success message on the connector settings page.

Br,
Joakim

[joakim.djuvfelt]

Connector page:

[Nikolas]

@joakim.djuvfelt

Can I ask you to check the correctness of the data entered in alfresco-global.properties and local.json (Jwt secret)? It’s possible that the entered data is different.

Also, please check the correctness of the jwt secret in local.json:

...
      "token": {
        "enable": {
          "request": {
            "inbox": true,
            "outbox": true
          },
          "browser": true
        },
        "inbox": {
          "header": "Authorization"
        },
        "outbox": {
          "header": "Authorization"
        }
      },
      "secret": {
        "inbox": {
          "string": "YOUR-JWT-SECRET"
        },
        "outbox": {
          "string": "YOUR-JWT-SECRET"
        },
        "session": {
          "string": "YOUR-JWT-SECRET"
...

[joakim.djuvfelt]

Hello Nikolas,

The secret is the same in both places, is there anywhere else we should have added it other than alfresco-global.properties and local.json?

Br,
Joakim

[Nikolas]

Even adding to alfresco-global.properties is optional.

1. Can I ask you personally to send me alfresco-global.properties and local.json in private messages
2. When disabling the jwt token verification, documents are still not edited?
   To disable the Jwt token in the local file.json needs to change the values of inbox outbox and browser: true to false and restart the document server.
   For deb: systemctl restart ds-*
   For Docker: supervisorctl restart all

You also need to remove the onlyoffice.jwtsecret=******** from the alfresco-global.properties file and restart alfresco

and re-check the connection from /alfresco/s/onlyoffice/onlyoffice-config

[joakim.djuvfelt]

Hello,

Thank you for the update.
The issue for us was the proxy configuration, the proxy did not allow onlyoffice server to connect. After that was fixed it is now up and running.

Br,
Joakim

[Nikolas]

Hey ,
We are glad that the problem was solved.
Thank you for the addition with your solution