Seafile CE 8.0.2 breaks OnlyOffice integration with security token

[Tjelfe]

After Upgrading to CE 8.0.2 (from 7.1.5) OnlyOffice integration is broken when secured via security token.
Configuration in seahub_settings.py:
ONLYOFFICE_JWT_SECRET = ‘mySecret’

OnlyOffice is deployed using docker with a custom local.json where the security token is defined.

Accessing an office dokument from Seafile web interface leads to an error message 'The documents security token is not correct. Please contact your system administrator.'

OnlyOffice integration with disabled security token still works.

[killing]

This will be fixed in 8.0.3 version.

[jobenvil]

@killing Can somebody confirm that it works with 8.0.3? Now I get following errors. I found out while testing the rpi version with tags 8.0.3-server

[chendelin1982]

I use Seafile8.0.4 community, connect OnlyOffice by http (not https), the error below

then, I modify onlyofficedocumentserver, set - JWT_ENABLED=flase, and I can edit docs

version: '3'
services:     
  onlyoffice-document-server:
    container_name: onlyoffice-docs
    image: onlyoffice/documentserver:6.0.2
    stdin_open: true
    tty: true
    restart: always
    environment:
     - JWT_ENABLED=flase
     - JWT_SECRET=jwt_secret
     - JWT_HEADER=AuthorizationJwt
    ports:
     - '9003:80'
    expose:
      - '80'
      - '443'
    volumes:
       - ./document_data:/var/www/onlyoffice/Data
       - ./document_log:/var/log/onlyoffice
       - ./document_fonts:/usr/share/fonts/truetype/custom
       - ./document_forgotten:/var/lib/onlyoffice/documentserver/App_Data/cache/files/forgotten