Storage integration
ownCloud and oCIS Coming soon
Status of ownCloud 10 and oCIS integration: not in v1; oCIS needs a proof key that v1 does not provide.
The feature described on this page is coming soon; it is not part of v1.
Connecting O3O Office Online to ownCloud and oCIS is not part of v1. There is no verified guide, no compose profile, and the v1 editor server has no proof key, which oCIS requires.
oCIS (ownCloud Infinite Scale)#
oCIS speaks WOPI through a separate service called collaboration, which runs outside the main oCIS process. It checks the X-WOPI-Proof signature on WOPI calls, so the editor server needs a proof key and discovery must publish a proof-key element. The v1 Docker bundle does not mount such a key; the command below lets you check.
# Count proof-key elements in discovery. v1 returns 0: the editor server has no proof key yet.
curl -s http://localhost:8080/hosting/discovery | grep -c "proof-key"Provisioning and syncing a proof key for the editor server, a compose profile for the oCIS collaboration service, and a verified guide.
ownCloud 10 (classic)#
ownCloud 10 has its own office app built on the same WOPI idea: set the editor server address in ownCloud, add the ownCloud origin to an aliasgroupN on the O3O side. The v1 cycle has not tested this pairing, so we do not publish exact commands yet.
A verified guide for ownCloud 10.
Meanwhile#
- If your system has an API to read and write files, the O3O.Editor embed layer opens files by URL and returns edited copies through a callback, no WOPI required.
- If you want to keep permissions on your side, write a small WOPI host in front of your file store.