Make Nextcloud and Onlyoffice work without proper certificates

We want to test NC+OO integration functionality without proper certs. Right now OO will complain like this without proper certs:

Here's a solution, I din't look deep into it though: https://help.nextcloud.com/t/make-nextcloud-onlyoffice-app-accept-self-signed-certificates/83020/12

changed milestone to %Backlog

added Certificates label

The concerning thing is that we have a green behave test but OO shows these failures...

The current behave test does not go as "deep" as this: it only checks if OO is opened inside NC. That's the most important part from an OAS perspective, because it means:

• both the NC and OO server are up-and-running
• OO plugin is enabled
• OO plugin is configured correctly

There's also the documentation about TLS usage for the onlyoffice docker image

mentioned in issue #965 (closed)

added Discussion label

In that nextcloud thread somebody suggests to:

1. Set USE_UNAUTHORIZED_STORAGE to true
2. Set ONLYOFFICE_HTTPS_HSTS_ENABLED to false

If our OO helm chart supports this, that could be a simple solution.

If our OO helm chart supports this, that could be a simple solution.

I just remembered that this is our own chart, so we're OK there

I just gave it a try, manually edited the nc-onlyoffice-documentserver deployment in the pipeline-droplet for openappstack!351 and added these env vars:

      - name: USE_UNAUTHORIZED_STORAGE
        value: "true"
      - name: ONLYOFFICE_HTTPS_HSTS_ENABLED
        value: "false"

And:

added 1 deleted label and removed Discussion label

added Doing label and removed 1 deleted label

assigned to @varac

changed milestone to %0.6.0

unassigned @varac

assigned to @varac

mentioned in commit c9625c7a

mentioned in commit 26fa2fae

mentioned in merge request !33 (merged)

added QA label and removed Doing label