Signature
ONLYOFFICE Docs uses tokens generated using the JSON Web Tokens standard. The tokens are sent when performing the client-side browser requests to ONLYOFFICE Docs or the HTTP requests to or from ONLYOFFICE Docs.
This feature is used in ONLYOFFICE Docs starting with version 4.2.
For the validation setup, it is necessary to edit the secret key and token parameters in the configuration file, which can be found (or created) at the following path:
- Linux
- Windows
/etc/onlyoffice/documentserver/local.json
%ProgramFiles%\ONLYOFFICE\DocumentServer\config\local.json
The default values are available in the default.json configuration file, which is available in the folders above (for Linux and Windows). Please do not edit the contents of the default.json file directly. The default values will be restored each time you restart Docker container or upgrade ONLYOFFICE Docs to a new version and all your changes will be lost.
Restart the services for the config changes to take effect:
- Docker
- RPM/DEB packages
supervisorctl restart all
systemctl restart ds-*
Parameters
| Parameter | Type | Example | Description |
|---|---|---|---|
| services.CoAuthoring.secret.browser.string | string | secret | Defines the secret key to generate a token in the client-side browser requests to ONLYOFFICE Docs. |
| services.CoAuthoring.secret.inbox.string | string | secret | Defines the secret key to generate a token in the incoming HTTP requests with the commands from the document storage service to the document command service, document conversion service and document builder service. |
| services.CoAuthoring.secret.outbox.string | string | secret | Defines the secret key to generate a token in the outgoing HTTP requests to the callbackUrl address by document editing service. |
| services.CoAuthoring.token.enable.browser | boolean | false | Defines if a token in the client-side browser requests is enabled or not. |
| services.CoAuthoring.token.enable.request.inbox | boolean | false | Defines if a token in the incoming HTTP requests is enabled or not. |
| services.CoAuthoring.token.enable.request.outbox | boolean | false | Defines if a token in the outgoing HTTP requests is enabled or not. |
Sample local.json configuration
{
"services": {
"CoAuthoring": {
"secret": {
"browser": {
"string": "secret"
},
"inbox": {
"string": "secret"
},
"outbox": {
"string": "secret"
}
},
"token": {
"enable": {
"browser": true,
"request": {
"inbox": true,
"outbox": true
}
}
}
}
}
}
Code samples for signature generation
Below you can find examples of signature generation for initialization config and requests. They are taken from test samples in different programming languages. We advise you to use this code in your projects to generate signatures.
- Node.js
- JavaScript
- C#
- Java
- PHP
- Python
- Ruby
- Go
import config from "config"
const configServer = config.get("server")
const cfgSignatureSecretExpiresIn = configServer.get("token.expiresIn")
const cfgSignatureSecret = configServer.get("token.secret")
const cfgSignatureSecretAlgorithmRequest = configServer.get("token.algorithmRequest")
documentService.getToken = function getToken(data) {
const options = {algorithm: cfgSignatureSecretAlgorithmRequest,
expiresIn: cfgSignatureSecretExpiresIn}
return jwt.sign(data, cfgSignatureSecret, options)
}
(async () => {
config.token = await createJWT(config, "JWT_SECRET");
})();
async function createJWT(json, secret) {
if (!secret) return null;
let header = {
typ: "JWT",
alg: "HS256"
}
let base64EncodeURL = function(str) {
return btoa(str).replace(/\+/g, '-').replace(/\//g, '_').replace(/\=/g, '');
}
let encodedHeader = base64EncodeURL(JSON.stringify(header));
let encodedPayload = base64EncodeURL(JSON.stringify(json));
let encoder = new TextEncoder();
let algorithm = { name: "HMAC", hash: "SHA-256" };
let key = await crypto.subtle.importKey("raw", encoder.encode(secret), algorithm, false, ["sign", "verify"]);
let buf = encoder.encode(encodedHeader + "." + encodedPayload);
let sign = await crypto.subtle.sign(algorithm.name, key, buf);
let hash = base64EncodeURL(String.fromCharCode(...new Uint8Array(sign)));
return encodedHeader + "." + encodedPayload + "." + hash;
}
public static class JwtManager
{
private static readonly string Secret;
public static readonly bool Enabled;
static JwtManager()
{
Secret = WebConfigurationManager.AppSettings["files.docservice.secret"] ?? "";
Enabled = !string.IsNullOrEmpty(Secret);
}
public static string Encode(IDictionary<string, object> payload)
{
var encoder = new JwtEncoder(new HMACSHA256Algorithm(),
new JsonNetSerializer(),
new JwtBase64UrlEncoder());
return encoder.Encode(payload, Secret);
}
}
public static String CreateToken(Map<String, Object> payloadClaims)
{
try
{
String secret = ConfigManager.GetProperty("files.docservice.secret");
Signer signer = HMACSigner.newSHA256Signer(secret);
JWT jwt = new JWT();
for (String key : payloadClaims.keySet())
{
jwt.addClaim(key, payloadClaims.get(key));
}
return JWT.getEncoder().encode(jwt, signer);
}
catch (Exception e)
{
return "";
}
}
<?php
function jwtEncode($payload) {
return \Firebase\JWT\JWT::encode($payload, $GLOBALS["DOC_SERV_JWT_SECRET"], "HS256");
}
?>
def encode(payload):
return jwt.encode(payload, config.DOC_SERV_JWT_SECRET, algorithm='HS256')
@jwt_secret = Rails.configuration.jwtSecret
class << self
def encode(payload)
return JWT.encode payload, @jwt_secret, 'HS256'
end
end
type onlyofficeJwtManager struct {
key []byte
}
func (j onlyofficeJwtManager) Sign(payload interface {
Valid() error
}) (string, error) {
token := jwt.NewWithClaims(jwt.SigningMethodHS256, payload)
ss, err := token.SignedString(j.key)
if err != nil {
return "", errors.New("could not generate a new jwt")
}
return ss, nil
}