As a publisher I want TS to support the Real Simple Licensing (RSL) Open License Protocol (OLP)  #81

Description

Evaluate support for a publisher-managed Real Simple Licensing (RSL) license file and the Open License Protocol (OLP) at the edge. The proposal is for publishers to state machine-readable content terms and for Trusted Server to participate in the relevant licensing flow. The precise edge responsibility, deployment model, and commercial operations are still open.

Original references: RSL standard, RSL API, crawler guide, and encrypted-content guide. Review the current versions of those documents before choosing an implementation; this issue's original explanation is a proposal, not an approved protocol contract.

Proposed scope

• Define which publisher resources and clients are in scope, where the license file is hosted, and which OLP operations Trusted Server should expose or call.
• Specify how license verification, authentication, billing/reporting dependencies, and failure behavior fit the existing request path.
• Decide whether protected-content key management is in scope or requires a separate design.

Done when

• A reviewed integration design maps each selected RSL/OLP operation to an edge route, request data, response, and configuration owner.
• An implementation or a focused proof of concept validates the agreed flow against the current protocol, with unauthorized and unavailable-service cases covered.
• The publisher setup and operational limits are documented; any unselected RSL capabilities are split into follow-up tickets.

Affected area

Publisher content delivery, edge routes, and operator configuration.