This topic covers types of applications that you might choose to create as rights-enabled.
The following application types are currently supported by Active Directory Rights Management Services SDK 2.1
A simple application could be a command line tool built to encrypt a provided file. For an example of a simple, rights-enabled application see, IPCHelloWorld - an example application.
Server mode is meant for non-interactive applications that consume, protect or process RMS-protected content. An example would be a Data Loss Prevention application that runs as a service on a file server and automatically protects sensitive documents. See the IpcDlp sample for an example of this application type.
If your application uses the server mode, it should authenticate to the RMS server silently. Unlike the client mode, the AD RMS SDK 2.1 will not open a credential prompt when it fails to authenticate silently. Also, when running in server mode, no application manifest is needed.
For more information on setting the API security mode see, Setting the API security mode.
A rich client application allows users to view and manipulate data through a graphical user interface (GUI). Often, the data presented in this GUI is high-value and sensitive to theft or accidental exposure. Information protection support typically enhances existing scenarios but, is not the primary motivation for developing the application.
Using AD RMS SDK 2.1 with rich client applications helps you:
Ensure that this data is always encrypted.
Prevent users from extracting data to an unprotected format (for example, prevent using the clipboard to copy and paste).
Microsoft Notepad is a simple rich client application. Microsoft Office is a more complex rich client application.
For more information on protecting your application, see Understanding usage restrictions.
- Developer concepts
- IpcDlp sample
- IPCHelloWorld - an example application
- Setting the API security mode
- Understanding usage restrictions