2.5.1 Actors

Stakeholders (actors) that use the RMS protocols include users, computers, applications, servers, and services. The actors that participate in the RMS use cases are:

RMS user: A person who uses an RMS client application. The primary objectives of an RMS user are to be able to protect and consume protected content.

Client computer: A computer or device, such as a mobile phone, that hosts an RMS client application.

RMS client application: An application that acts as a client to an RMS server. The application can be an end user-based or server-based application and can perform RMS functions such as protecting content and providing access to protected content.

ISV application: An application that might or might not use the RMS client. An application can be an end-user client application or a server application that uses RMS.

RMS server: The component that provides RMS services, such as issuing certificates and licenses.

RMS administrator: A person who performs RMS administration in the enterprise and typically has full access to RMS servers. The RMS administrator configures the RMS server for use in RMS.

RMS cloud service: A Microsoft web service that provides enrollment services to RMS servers. All versions of the RMS server that precede version 2 contacted the Microsoft enrollment service to sign the SLC key into the hierarchy. The RMS version 2 server has a shared enrollment private key and certificate chain. Upon initialization of the RMS version 2 server, the server generates its own unsigned SLC, signs it with this shared enrollment private key, and appends the certificate chain.