Server applications that publish, consume, or process RMS-protected content. RMS client 1.0 SP2 Windows Vista Windows Server 2008 The following table identifies the features associated with each type of lockbox and with the SOAP APIs. If your server-based application publishes but does not consume protected content, you can use the SOAP APIs included with the SDK rather than a lockbox. Use a server lockbox for applications running on an AD RMS server that both publish and consume protected content. Use a client lockbox for applications running on a client. Server lockbox for the Production hierarchy. Server lockbox for the Pre-production hierarchy. Lockbox DLLĬlient lockbox for the Pre-production hierarchy.Ĭlient lockbox for the Production hierarchy. You can call DRMGetSecurityProvider to retrieve the path of the appropriate DLL for your certificate hierarchy (Production or Pre-production) and your operating system type (server or client). To create a secure environment, you can call DRMInitEnvironment and specify the lockbox path, the signed manifest, and the machine certificate.įour lockboxes are installed with AD RMS. The lockbox verifies all licenses and certificates used by the application and, for AD RMS clients, protects the process space by limiting access to required and optional modules identified in the application manifest. A lockbox is a dynamic link library (DLL) that can be used to increase the security of the environment in which an Active Directory Rights Management Services (AD RMS) application runs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |