2.5.4.12 Republishing Content - ISV Application
Goal
Create a new signed publishing license (PL) that has the same content key as an existing signed PL.
Context of use
This interface is useful when there is a need to alter the set of rights that was granted to users in the original PL without re-encrypting the content with a new content key.
Actors
Direct actor: The direct actor of this use case is the RMS client.
Primary actor: The primary actor is the same as the direct actor.
Supporting actors: The RMS server.
Stakeholders and interests
RMS user, as described in section 2.5.1.
ISV application, as described in section 2.5.1.
Client computer, as described in section 2.5.1.
RMS server, as described in section 2.5.1
Preconditions
The RMS server has been bootstrapped into the system.
The RMS client is authorized to call the EditIssuanceLicense service.
The RMS client has a signed PL that allows republishing.
The RMS client has an unsigned PL containing the new set of rights.
Minimal guarantees
The ISV application has a signed PL for the content. This PL contains the updated set of rights for the content. The PL contains the location of the RMS server to retrieve a use license to consume the content. The PL allows the intended recipient to consume the content.
Success guarantee
The success guarantee is the same as the minimal guarantee.
Main success scenario
Trigger: An RMS user replaces the set of rights granted by a PL without changing the content key that protects the content.
The ISV application uses the EditIssuanceLicense operation to request an updated PL from the RMS server, submitting both the signed PL used to protect the content and an unsigned PL used for the updated set of rights.
The RMS server adds the existing content key to the unsigned PL for the updated content, signs the PL, and returns it to the ISV application.
Extensions
None.