Skip to content

Security and data ​

This page is for the IT and security teams evaluating Save2ERP.

What travels where ​

  • The document goes from the user's computer to the Save2ERP server, then to the target system, always over HTTPS. The server never writes it to disk: it forwards it to the target system and does not keep it.
  • The user's credentials for the target system are only entered in the target system's sign-in window. Neither the pane nor the Save2ERP server see them.
  • The OAuth2 token obtained at sign-in stays on the server (see below).

Sign-in to the target system ​

  • Sign-in uses OAuth2 with PKCE. The user explicitly authorizes Word to save documents on their behalf, with their own permissions in the target system.
  • The token is encrypted (AES-256-GCM) and stored in a cookie the browser cannot read (httpOnly). Only the server decrypts it to call the target system: it is never exposed to the pane.
  • The server renews the token before it expires. The session lasts 7 days by default (OAUTH_COOKIE_MAXAGE). Signing out revokes the token with the target system.
  • The server only accepts declared systems, and only one session at a time: a document from another system is refused until the user signs out. The addresses called only come from the server's configuration: the pane cannot choose them.

Cookies ​

All cookies are signed, httpOnly, Secure, SameSite=None and prefixed with __Host-: the browser only accepts them from the server itself, over HTTPS. Details are in Cookies.

Request protection ​

  • Requests that change something (upload, sign-out) only accept JSON: a third-party page cannot trigger them with the user's cookies.
  • An upload without a session is refused before the document is even read.
  • The server's security headers only allow the pane to be displayed within Microsoft Office domains.
  • The server always checks the certificates of the systems it calls.

Stored data ​

DataWhereContent
Configuration.env on the serverOAuth2 secrets and keys: to be protected (permissions limited to the service account).
User registerdata/license-users.json, limited license onlyA hash (SHA-256) of the organization and of the Microsoft ID of each user, with the dates of first and last use. No name, no e-mail address.
Logslogs/ on the serverStartup, sign-ins, uploads and errors. Not the content of documents.
User optionsWord's local storage, on the computerAction on duplicates and default format.

Microsoft identity ​

Only with a license limited by number of users:

  • the pane obtains a Microsoft token for the user through a Save2ERP application registered in Microsoft Entra ID, authorized by the administrator (see Deploying in Microsoft 365);
  • the server checks the token's signature, audience, issuer and scope, and that the user belongs to the license's organization;
  • the token is only used to count the user: it gives access to no other Microsoft 365 data.

With an unlimited license, no Microsoft identity is requested.