Proof keys

To restrict public access to your data, a secure exchange of requests between an online office and an integrator must be configured.

The integrator must check that the request is received from ONLYOFFICE Docs. It uses proof keys for this purpose. ONLYOFFICE Docs signs the request with a private key. The corresponding public key is written in the proof-key element in the WOPI discovery XML. The integrator checks the private key with the public key. The signature is sent with every request in the X-WOPI-Proof and X-WOPI-ProofOld HTTP headers. Private and public keys are set up via the following config parameters:

Parameters

NameTypeExampleDescription
wopi.publicKeystring"public key example"Defines the public key that the integrator uses to check the private key.
wopi.modulusstring"modulus example"Defines the RSA modulus in the Base64-encoded format that is used to retrieve the public key.
wopi.exponentstring"AQAB"Defines the RSA exponent in the Base64-encoded format that is used to retrieve the public key.
wopi.privateKeystring"private key example"Defines the private key that signs the ONLYOFFICE Docs request.

Example

{
  "wopi": {
    "publicKey": "public key example",
    "modulus": "modulus example",
    "exponent": "AQAB",
    "privateKey": "private key example"
  }
}

By default, proof keys are already set. They are not generated, i.e. the same keys are used for all installations.

Get Help

  • If you have any questions about ONLYOFFICE Docs, try the FAQ section first.
  • You can request a feature or report a bug by posting an issue on GitHub.
  • You can also ask our developers on ONLYOFFICE forum (registration required).