HP MFP Digital Sending Software (DSS) 5.0 - Configure DSS 5 to use Adobe LiveCycle Rights Management

ManualsBrandsHP ManualsSoftwareHP MFP Digital Sending Software 5.0

Page 1 of 6 white paper



Introduction

LiveCycle is an Adobe product that can provide many functions. One of the most important

functions of LiveCycle is to act as a document management system that provides control and

security to the PDF files it manages. An important part of the security structure is for LiveCycle to

create policies which are attached to the files. Using policies for security is part of the LiveCycle

function of Rights Management.

DSS can be configured to route pdf files through a LiveCycle server prior to sending the file on to its

destination. This allows a Rights Management policy to be applied to the pdf files sent via DSS. The

flow is:

1. If DSS is to send a pdf file to a destination it checks to see if it is configured to send the file

to a LiveCycle server first to have a policy applied to the document

2. If DSS is configured to use LiveCycle it will send the document to the LiveCycle server with

other information as configured in DSS’s LiveCycle configuration file.

3. LiveCycle attaches the policy to the document and returns the document to DSS

4. DSS sends the document to its destination

This whitepaper discusses how to configure DSS to interact with a LiveCycle sever to have LiveCycle

policies applied.

This paper assumes the customer environment has a LiveCycle server configured properly and the

desired policy to apply to DSS documents already defined. This paper also assumes the DSS admin

configuring DSS for LiveCycle understands LiveCycle concepts and the specific configuration of the

server to be used to apply policies.

Overview

PDF files can flow through DSS to several different destinations including email servers, shared

folders, ftp sites and Microsoft SharePoint sites. If OCR is not being used the PDF files are created

by the sending device and transferred to DSS to send to the final destination. If OCR is used then

the OCR engine on the DSS server creates the PDF files which are then sent to their destinations.

Interaction with LiveCycle to have a policy applied to PDF files can be configured on / off by

destination type. For example, using the LiveCycle server can be enabled for send to email jobs but

disabled for PDF files going to any other destination type.

White Paper

Configuring DSS 5 for Rights

Management using Adobe

LiveCycle

Security Level: Public

Date Written: 12/1/2013

Document Summary

 Describes how to configure DSS 5 to send PDF documents to Adobe LiveCycle to have a policy

applied

 Etc…

Summary of content (6 pages)

PAGE 1
White Paper Configuring DSS 5 for Rights Management using Adobe LiveCycle  Security Level: Public Date Written: 12/1/2013 Document Summary Describes how to configure DSS 5 to send PDF documents to Adobe LiveCycle to have a policy applied    Etc… Introduction LiveCycle is an Adobe product that can provide many functions. One of the most important functions of LiveCycle is to act as a document management system that provides control and security to the PDF files it manages.
PAGE 2
Configuration File The LiveCycle configuration file is located at the following location: \Program Files (x86)\Hewlett-Packard\HP Digital Sending Software\Filesystems\Product\Dss\Configuration\HP.Dss.App.RightsManagement.config This file has been created with future expansion in mind. There are many XML elements that can possibly be configured for multiple values in the future but only one value is applicable at this time.
PAGE 3
Encrypted element, on line 49, to be False. When this value is False DSS will encrypt the value in the password element so that a password is not stored in clear text on the DSS server’s disk. DSS will also change the value of the encrypted element to be TRUE. The check of this value and subsequent encryption is done when the DSS service restarts. The DSS service must always be restarted for DSS to see any changes made to this configuration file.
PAGE 4
DSS sends a user name and domain to LiveCycle with each file. A default user name and domain are specified on lines 89 and 90. If line 88, the UseDefaultPublisher element, is set to false then DSS sends the signed in user’s user name and domain to LiveCycle if they exist, and sends the default user name and domain if the sign in information does not exist. If the UseDefaultPublisher element in line 88 is set to true then the default user name and domain are always sent.
PAGE 5
The Default Configuration File with Line Numbers Page 5 of 6 white paper
PAGE 6
Page 6 of 6 white paper