Open-Xchange App Suite Integration?

[brock0124]

I noticed some config variables for the Open Xchange App Suite API -- is there a planned integration for that? Otherwise, what are the variables for? I run App Suite as my webmail client, but dislike their OX Drive & Office Suite. So, if OpenCloud could replace that part, it'd be really cool.

The variables are located near the bottom of this list: https://docs.opencloud.eu/docs/dev/server/services/web/environment-variables

[mohammadrezwankhan]

Those variables configure a released but narrow contact/mail integration. They do not make OpenCloud a replacement backend for OX Drive or OX Office.

In OpenCloud server 7.4.0 with web 7.3.0, the intended configuration is:

WEB_OPTION_OX_APP_SUITE_ENABLED: "true"
WEB_OPTION_OX_APP_SUITE_API_URL: "https://your-ox-host/<middleware-api-base>"

The URL must be the OX Middleware HTTP API base for which appending /addressbooks and /mail/compose reaches those APIs; it is not the normal App Suite UI URL unless that URL is also your API base.

What the released integration does is:

1. While sharing an OpenCloud file or folder, search the OX address book using its autocomplete endpoint.
2. Show matching OX contacts as external/virtual contacts.
3. For a selected contact, create a read-only OpenCloud public link rather than an OpenCloud user/group share.
4. Use OX Mail Compose to email that link to the contact.

That behavior is documented in the merged OX contact-invite PR and matches the released client's two OX operations: addressbooks autocomplete and mail/compose.

Two deployment details matter:

• These are web-service/frontend options, not OX credentials. The browser calls the configured OX API and the OpenCloud client adds its dynamic bearer/request headers, so the API must be browser-reachable and your OX/auth proxy must accept that authentication and CORS arrangement.
• If you set WEB_UI_CONFIG_FILE, that config file takes precedence over the WEB_OPTION_* environment variables. Check the rendered OpenCloud config.json in the browser before debugging OX itself; options.oxAppSuite.enabled should be true and apiUrl should be populated. Do not paste tokens when checking it.

A practical verification is to open browser DevTools, invite a non-OpenCloud email/contact while sharing a normal file, and confirm requests go to <apiUrl>/addressbooks?... followed—after selecting the contact—by <apiUrl>/mail/compose.... A missing URL suppresses contact results and prevents mail sending.

I could not find a published release or roadmap commitment that extends this to replacing OX Drive or OX Office. The current public implementation is specifically contact lookup plus delivery of an OpenCloud public link. So the variables are useful with your App Suite deployment today, but they do not indicate storage/editor integration by themselves.

[brock0124]

Awesome- thank you so much for the detailed explanation! That is a unique integration for sure, and I can't think of a fitting use-case for myself, but I'm sure there are plenty of folks who could leverage it. I'd love to see that integration expanded, but either way, I appreciate everything OpenCloud offers so far.