Online editing for a content management system

A system for direct desktop client integration with an on-premises content management system, the system comprising:

• a remote editing service server and an on-premises Online Editing Service (OES) connector service configured to:
• receive, at the remote editing service server, login information transmitted from a native desktop client application;
• initiate, by the remote editing service server, an authentication request by calling the OES connector service via a secure REST API endpoint and passing an authentication token request;
• return, by the OES connector service, a scoped JSON Web Token (JWT) to the remote editing service server;
• validate, by the OES connector service upon successful token validation, on-premises permissions of the user by querying access control lists in the on-premises content management system repository;
• generate, by the OES connector service when the user is authorized, a signed folder manifest containing only the authorized folder structure, document metadata, and direct-access pointers to the on-premises storage;
• and
• return the signed folder manifest to the remote editing service server, which forwards the manifest to the native desktop client application so that the authorized folder structure and documents are rendered directly in the native desktop client application without routing through a web-based client.

A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a remote editing service server and an on-premises Online Editing Service (OES) connector service, cause the one or more processors to perform the following operations for direct desktop client integration with an on-premises content management system:

• receiving, at the remote editing service server, login information transmitted from a native desktop client application;
• initiating, by the remote editing service server, an authentication request by calling the OES connector service via a secure REST API endpoint and passing an authentication token request;
• returning, by the OES connector service, a scoped JSON Web Token (JWT) to the remote editing service server;
• validating, by the OES connector service upon successful token validation, on-premises permissions of the user by querying access control lists in the on-premises content management system repository;
• generating, by the OES connector service when the user is authorized, a signed folder manifest containing only the authorized folder structure, document metadata, and direct-access pointers to the on-premises storage;
• and
• returning the signed folder manifest to the remote editing service server, which forwards the manifest to the native desktop client application so that the authorized folder structure and documents are rendered directly in the native desktop client application without routing through a web-based client.