|
Policies can be designed so that users must be logged in
to Rights Management to open protected documents. Securing documents
for online use employs a straightforward process for encrypting
the document and providing access only to authenticated and authorized
users.
The steps in the diagram are as follows:
The document owner or administrator decides to secure
the document from a supported client application with a policy that
allows online use. Users can apply policies to documents by using
any supported client application. Developers can also protect documents
with policies by using the Rights Management service in a process
or programmatically by using the Rights Management Service API.
Rights Management creates a document license and document
keys, and encrypts the policy. The document license, document key,
and encrypted policy are returned to the client application.
The
document license is an XML document that identifies the protected document,
the policy, and the identity of the server. The server digitally
signs the license to ensure data integrity.
The document
key is a symmetric key for encrypting the document. Each protected
document has an associated document key.
The client application uses the document key to encrypt the
document, discards the document key, and embeds the document license
and policy. These tasks are performed in a web page or supported
client application.
If the policy specifies that document events are logged, the
client software sends event information to the server for logging
as soon as the user opens the document. For information about the
audit log, see Monitoring events in LiveCycle Administration Console Help.
|
|
|
