Collaboration

Table of Contents

Introduction
Default Values
Requirements
WOPI Configuration
Configuration
- Environment Variables
- YAML Example

Introduction

The collaboration service connects Infinite Scale with document servers such as Collabora and ONLYOFFICE using the WOPI protocol.

Since this service requires an external document server, it won’t start by default when using ocis server (supervised mode). You must start it manually with the ocis collaboration server command.

Default Values

The collaboration service listens on port 9300 by default.

Requirements

The collaboration service requires the target document server (ONLYOFFICE, Collabora, etc.) to be up and running. Additionally, some Infinite Scale services are also required to be running in order to register the GRPC service for the open in app action in the webUI. The following internal and external services need to be available:

External document server
gateway service.
app provider service.

If any of the named services above have not been started or are not reachable, the collaboration service won’t start. For the binary or the docker release of Infinite Scale, check with the List running services command if they have been started. If not, you must start them manually upfront before starting the collaboration service.

WOPI Configuration

There are a few variables that you need to set:

COLLABORATION_WOPIAPP_ADDR:
The URL of the WOPI app (onlyoffice, collabora, etc).
For example: https://office.example.com.
COLLABORATION_HTTP_ADDR:
The external address of the collaboration service. The target app (onlyoffice, collabora, etc) will use this address to read and write files from Infinite Scale.
For example: https://wopiserver.example.com.
COLLABORATION_HTTP_SCHEME:
The scheme to be used when accessing the collaboration service. Either http or https. This will be used to finally build the URL that the WOPI app needs in order to contact the collaboration service.

The rest of the configuration options available can be left with the default values.

Configuration

Environment Variables

The collaboration service is configured via the following environment variables. Read the Environment Variable Types documentation for important details. Column IV shows with which release the environment variable has been introduced.

master + Rolling 6.1.0

Deprecation notes for the collaboration service
Deprecation Info	Deprecation Version	Removal Version	Deprecation Replacement
COLLABORATION_CS3API_GATEWAY_NAME removed for simplicity.	6.0	next-prod

Environment variables for the collaboration service
Name	IV	Type	Default Value	Description
`COLLABORATION_APP_NAME`	6.0.0	string	Collabora	The name of the app, either Collabora, OnlyOffice, Microsoft365 or MicrosoftOfficeOnline
`COLLABORATION_APP_DESCRIPTION`	6.0.0	string	Open office documents with Collabora	App description
`COLLABORATION_APP_ICON`	6.0.0	string	image-edit	Icon for the app
`COLLABORATION_APP_LOCKNAME`	6.0.0	string	com.github.owncloud.collaboration	Name for the app lock
`COLLABORATION_APP_ADDR`	6.0.0	string	https://127.0.0.1:9980	The URL where the WOPI app is located, such as https://127.0.0.1:8080.
`COLLABORATION_APP_INSECURE`	6.0.0	bool	false	Skip TLS certificate verification when connecting to the WOPI app
`COLLABORATION_APP_PROOF_DISABLE`	6.0.0	bool	false	Disable the proof keys verification
`COLLABORATION_APP_PROOF_DURATION`	6.0.0	string	12h	Duration for the proof keys to be cached in memory, using time.ParseDuration format. If the duration can’t be parsed, we’ll use the default 12h as duration
`OCIS_JWT_SECRET` `COLLABORATION_JWT_SECRET`	pre5.0	string		The secret to mint and validate jwt tokens.
`COLLABORATION_GRPC_ADDR`	6.0.0	string	127.0.0.1:9301	The bind address of the GRPC service.
`COLLABORATION_HTTP_ADDR`	6.0.0	string	127.0.0.1:9300	The bind address of the HTTP service.
`OCIS_HTTP_TLS_ENABLED`	pre5.0	bool	false	Activates TLS for the http based services using the server certifcate and key configured via OCIS_HTTP_TLS_CERTIFICATE and OCIS_HTTP_TLS_KEY. If OCIS_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.
`OCIS_HTTP_TLS_CERTIFICATE`	pre5.0	string		Path/File name of the TLS server certificate (in PEM format) for the http services.
`OCIS_HTTP_TLS_KEY`	pre5.0	string		Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.
`COLLABORATION_WOPI_SRC`	6.0.0	string	https://localhost:9300	The WOPISrc base URL containing schema, host and port. Set this to the schema and domain where the collaboration service is reachable for the wopi app, such as https://office.owncloud.test.
`COLLABORATION_WOPI_SECRET`	6.0.0	string		Used to mint and verify WOPI JWT tokens and encrypt and decrypt the REVA JWT token embedded in the WOPI JWT token.
`COLLABORATION_WOPI_DISABLE_CHAT` `OCIS_WOPI_DISABLE_CHAT`	next	bool	false	Disable chat in the frontend.
`OCIS_REVA_GATEWAY` `COLLABORATION_CS3API_GATEWAY_NAME` Deprecation Note	6.0.0	string	com.owncloud.api.gateway	CS3 gateway used to look up user metadata.
`COLLABORATION_CS3API_DATAGATEWAY_INSECURE`	6.0.0	bool	false	Connect to the CS3API data gateway insecurely.
`OCIS_TRACING_ENABLED` `COLLABORATION_TRACING_ENABLED`	6.0.0	bool	false	Activates tracing.
`OCIS_TRACING_TYPE` `COLLABORATION_TRACING_TYPE`	6.0.0	string		The type of tracing. Defaults to '', which is the same as 'jaeger'. Allowed tracing types are 'jaeger' and '' as of now.
`OCIS_TRACING_ENDPOINT` `COLLABORATION_TRACING_ENDPOINT`	6.0.0	string		The endpoint of the tracing agent.
`OCIS_TRACING_COLLECTOR` `COLLABORATION_TRACING_COLLECTOR`	6.0.0	string		The HTTP endpoint for sending spans directly to a collector, i.e. http://jaeger-collector:14268/api/traces. Only used if the tracing endpoint is unset.
`OCIS_LOG_LEVEL` `COLLABORATION_LOG_LEVEL`	6.0.0	string		The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.
`OCIS_LOG_PRETTY` `COLLABORATION_LOG_PRETTY`	6.0.0	bool	false	Activates pretty log output.
`OCIS_LOG_COLOR` `COLLABORATION_LOG_COLOR`	6.0.0	bool	false	Activates colorized log output.
`OCIS_LOG_FILE` `COLLABORATION_LOG_FILE`	6.0.0	string		The path to the log file. Activates logging to this file if set.
`COLLABORATION_DEBUG_ADDR`	6.0.0	string	127.0.0.1:9304	Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.
`COLLABORATION_DEBUG_TOKEN`	6.0.0	string		Token to secure the metrics endpoint.
`COLLABORATION_DEBUG_PPROF`	6.0.0	bool	false	Enables pprof, which can be used for profiling.
`COLLABORATION_DEBUG_ZPAGES`	6.0.0	bool	false	Enables zpages, which can be used for collecting and viewing in-memory traces.

YAML Example

Note that the filename shown below has been chosen on purpose.
See the Configuration File Naming for details when setting up your own configuration.
See the Notes for Environment Variables if you want to use environment variables in the yaml file.

master + Rolling 6.1.0

# Autogenerated
# Filename: collaboration-config-example.yaml

app:
  name: Collabora
  description: Open office documents with Collabora
  icon: image-edit
  lockname: com.github.owncloud.collaboration
  addr: https://127.0.0.1:9980
  insecure: false
  proofkeys:
    disable: false
    duration: 12h
token_manager:
  jwt_secret: ""
grpc:
  addr: 127.0.0.1:9301
http:
  addr: 127.0.0.1:9300
  tls:
    enabled: false
    cert: ""
    key: ""
wopi:
  wopisrc: https://localhost:9300
  secret: ""
  disable_chat: false
cs3api:
  gateway:
    name: com.owncloud.api.gateway
  datagateway:
    insecure: false
tracing:
  enabled: false
  type: ""
  endpoint: ""
  collector: ""
log:
  level: ""
  pretty: false
  color: false
  file: ""
debug:
  addr: 127.0.0.1:9304
  token: ""
  pprof: false
  zpages: false