Seafile Linux Client SSO Failure

Hi, I’m using Seafile server behind Caddy + Authelia, and the Linux/Windows/Android clients. The setup works correctly in all platforms except Linux, where SSO fails. Some background information:

https://forum.seafile.com/t/seadrive-cannot-login-via-sso-in-linux-gnome-wayland/23796/9

Local browser server setting doesn’t really help, unfortunately.

I have used LLMs to diagnose the issue, and I’m sharing it below as it sounds like a feasible scenario, and could be useful (my domain name has been redacted). I’m happy to help, just let me know how! Thanks in advance.

Possible root cause

JavaScript syntax incompatibility between the Authelia portal bundle and the embedded browser engine.

  • The Seafile Linux AppImage embeds Qt 5 WebEngine = Chromium 83 (May 2020). Verified in the mounted AppImage: libQt5WebEngineCore.so.5, Chrome/83.0.4103.122.

  • The Authelia v5 portal (index.CXslS62G.js) is built with Vite’s modern target and contains ES2021 logical assignment operators: 47× ||=, 13× ??=, 15× &&=. These require Chrome ≥ 85.

  • The whole bundle therefore fails to parse in the embedded view, so the portal SPA never renders and its post-login redirect to the rd= return URL never fires.

Direct evidence from ~/.ccnet/logs/applet.log:

Uncaught SyntaxError: Unexpected token '=' (https://<mydomain>.com/static/js/index.CXslS62G.js:2)

Why other platforms work

Platform Embedded engine ES2021 support
Linux AppImage Qt5 WebEngine / Chromium 83 ✗ (needs ≥85)
Windows Qt 6.5 WebEngine / Chromium ~108 ✓
macOS Qt 6 / Chromium ~108 ✓
Android System WebView (current Chrome) ✓

Seafile moved its Windows/macOS builds to Qt6; the Linux AppImage is still on Qt5. This is a stale-toolchain issue in the third-party binary we cannot rebuild.

Thanks for reporting the issue. We will give it a check soon.