Skip to main content
Version: Any 26

Server access

This module describes how to connect to an external service: its URL and how to authenticate to it.

It is the single place where this information is stored. The modules consuming a service (AI, signature, archiving, OCR, external content resolution) never carry a URL or a secret themselves: they point to a server access defined here. A single access serves every application.

API access:

Access URL: enter the URL to reach the server
Purpose: choose a use in the list and enter the parameters requested for that use

JWT:

Enable JSON Web Token:
A JSON Web Token negotiates a temporary access token with the remote API.
It requires an RSA private / public key pair to certify that the request for a new token is made by us.
Once generated, only the public key is needed by the target API to decrypt our initial request.

RSA key pair:
An RSA public / private key pair is generated on save. It is stored securely in Any and, only afterwards, the public part of the key can be copied, in PEM format.
The private key encrypts the header and the payload of the JWT and signs the request. Only the public key is needed by the third party to check that our token request has not been tampered with.

Claims:
The payload of the token is a "name/value" JSON made of predefined claims (iss, exp, sub, aud, nbf, iat, jti), public or private.
The iat and exp claims are added automatically.