bb c Installing and Deploying Adobe Flash

bb c Installing and Deploying Adobe Flash
bc
Installing and Deploying Adobe® Flash®
Media Rights Management Server
Adobe® Flash® Media Rights Management Server
November 2008
Version 1.5
© 2008 Adobe Systems Incorporated. All rights reserved.
Adobe® Flash® Media Rights Management Server 1.5 Installing and Configuring Flash Media Rights Management Server for Microsoft®
Windows®, Linux®, and UNIX®
Edition 2.0, November 2008
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Adobe AIR, Flash, and LiveCycle are either registered trademarks or trademarks of Adobe Systems Incorporated in
the United States and/or other countries.
Intel and Pentium are registered trademarks of Intel Corporation in the U.S. and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Oracle is a trademark of Novell, Inc.
Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries.
Sun and Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the US and other countries.
All other trademarks are the property of their respective owners.
Protected by U.S. patents 5,200,740; 5,233,336; 5,255,357; 5,929,866; 5,943,063; 6,563,502; 6,754,382; 7,002,597; 7,006,107; 7,071,941;
7,305,617; 7,333,110; 7,353,287; 7,434,048. Patents Pending in the U.S. and/or other countries.
This product contains either BSAFE and/or TIPEM software by RSA Security Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/)
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 4
Who should read this document? ............................................................................................................................................ 4
Conventions used in this document ....................................................................................................................................... 4
Additional information................................................................................................................................................................. 5
1
System Requirements ................................................................................................................. 6
Minimum hardware requirements........................................................................................................................................... 6
Intel x86 compatibility.................................................................................................................................................................. 6
Recommended hardware requirements ............................................................................................................................... 6
Supported software....................................................................................................................................................................... 7
Web browser support ................................................................................................................................................................... 8
Additional requirements for Linux operating systems..................................................................................................... 8
Installing from network drives................................................................................................................................................... 8
Installing on a cluster.................................................................................................................................................................... 9
Configuration worksheet............................................................................................................................................................. 9
2
Installing Flash Media Rights Management Server ................................................................ 10
Installing LiveCycle ES Update 1.............................................................................................................................................10
Installing LiveCycle ES Update 1 Service Pack 1................................................................................................................11
Installing Flash Media Rights Management Server..........................................................................................................11
3
Post-Deployment Tasks ............................................................................................................ 12
Configuring SSL ............................................................................................................................................................................12
Configuring Flash Media Rights Management Server ....................................................................................................12
Modifying the config.xml file.............................................................................................................................................12
Configuring the server for multiple tenant support ...........................................................................................13
Creating the Packager User................................................................................................................................................14
Configuring the credentials......................................................................................................................................................15
Replacing expired credentials ...........................................................................................................................................15
Switching from temporary to permanent credentials .............................................................................................15
External authenticators and authorizers..............................................................................................................................16
Flash Media Rights Management Server tools ..................................................................................................................16
Uninstalling LiveCycle ES...........................................................................................................................................................16
3
About This Document
This guide provides instructions on how to install and configure Adobe® Flash® Media
Rights Management Server. Flash Media Rights Management Server provides content distributors with
the ability to protect FLV and F4V files that are delivered to Adobe Media Player and Adobe AIR™
applications.
Who should read this document?
This guide provides information for administrators or developers who are responsible for installing and
configuring Flash Media Rights Management Server. The information provided is based on the
assumption that anyone reading this guide is familiar with J2EE application servers, Microsoft® Windows®
or Linux® operating systems, Oracle®, MySQL, or SQL Server database servers, and web environments.
Most of the information about directory locations in this guide is cross-platform (all file names and paths
are case-sensitive on Linux). Any platform-specific information is indicated as required.
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Description
Default value
[appserver root]
The home directory of the application
server that runs the Adobe LiveCycle® ES
Update 1 (8.2) services.
These installation locations are
examples. Your installation location
may be different.
WebLogic Server on Windows:
C:\bea\wlserver_10.0\
WebLogic Server on Linux
/opt/bea/wlserver10.0
JBoss Application Server on Windows:
C:\jboss
JBoss Application Server on Linux:
/opt/jboss
[FMRMS root]
The installation directory where
Rights Management Server resides, as
well as the command line tools and SPI
library.
Windows: C:\Adobe\FMRMS1.5\
Linux: /opt/adobe/fmrms1.5/
4
Adobe Flash Media Rights Management Server
About This Document
Installing and Deploying Adobe Flash Media Rights Management Server
Additional information
Name
Description
Default value
[LiveCycleES root]
The installation directory that is used for Windows: C:\Adobe\LiveCycle8.2\
all LiveCycle ES solution components. The Linux: /opt/adobe/livecycle8.2/
installation directory contains
subdirectories for LiveCycle Configuration
Manager and each LiveCycle ES solution
component installed (along with the
product documentation). This directory
also includes directories that relate to
third-party technologies.
Most of the information about directory locations in this document is cross-platform (all file names and
paths are case-sensitive on Linux). Any platform-specific information is indicated as required.
Additional information
The resources in this table provide additional information about Flash Media Rights Management Server.
For information about
See
Flash Media Rights Management Server solution,
development environment, run-time environment,
and each Flash Media Rights Management Server
component
Overview
Managing administrative users and user roles
User Management Help
Customizing and configuring Flash Media Server
Adobe Flash Media Server Administration and
Configuration Guide
Creating custom service providers for Adobe
User Management and Adobe
LiveCycle Rights Management ES
Developing Service Providers
The Java interfaces and classes that are used to
create custom service providers
Adobe Flash Media Rights Management Server API
Reference
Securing video content by using the Flash Media
Securing Video Content
Rights Management Server command line tools and
Java APIs
Delivering content in Adobe Media Player
Adobe Media Player Content Developer Kit
Using Adobe Media Player to find and view content
Adobe Media Player Help
Flash Media Rights Management Server release
information and last-minute changes that occur to
the product
Release Notes
5
1
System Requirements
This section provides the information you require to prepare your server environment before you perform
the installation and deployment of Flash Media Rights Management Server.
Minimum hardware requirements
This table provides the minimum hardware requirement that Flash Media Rights Management Server
supports.
Operating system
Minimum hardware requirement
Microsoft Windows Server® 2003 Enterprise
Edition SP2 or Standard Edition SP2 and R2 Sp2
(32-bit edition only)
Intel® Pentium® 3 or x86 equivalent, 1 GHz
processor VMWare ESX Server and GSX Server
RAM - 2 GB
Free disk space - 2.7 GB of temporary space plus
1.7 GB for LiveCycle ES
Red Hat® Enterprise Linux AS or ES 4.0
(32-bit edition only)
Pentium 3 or x86 equivalent, 1 GHz processor
RAM - 2.5 GB
Free disk space - 2.7 GB of temporary space plus
1.7 GB for LiveCycle ES
Intel x86 compatibility
On supported Windows and Linux environments, Flash Media Rights Management Server supports Intel
EDT64 and AMD64 compatible chipsets, but the operating system must be 32-bit.
Recommended hardware requirements
In addition to the minimum hardware requirements listed previously, here are the recommended
hardware requirements for a small production environment:
Intel environments: Pentium 4, 2.8 GHz or greater. Using a dual core processor will further enhance
performance.
Memory requirements: 4 GB of RAM.
6
Adobe Flash Media Rights Management Server
System Requirements
Installing and Deploying Adobe Flash Media Rights Management Server
Supported software
Supported software
This table provides a summary of the application servers, web browsers, databases, database drivers, and
the Sun™ Java™ Development Kit (JDK) versions that Rights Management Server supports.
Required software
Supported version
Operating system
●
Microsoft Windows Server 2003 Enterprise Edition SP2 or Standard Edition
SP2 and R2 Sp2 (32-bit edition only)
●
Red Hat Enterprise Linux AS or ES 4.0 (32-bit edition only)
●
JBoss® 4.0.3 SP1
●
BEA WebLogic® 10 MP1
Application server
Web browser
See “Web browser support” on page 8.
JDK
For JBoss on all platforms:
●
Sun JDK 1.5.0_11 (or later version of the 1.5.0 release) available at Sun
Developer Network. Versions 1.4 and 1.6 are not supported.
For WebLogic on all platforms:
●
BEA JRockit® 5.0 R26.4 JDK and all later 5.0 releases of JRockit available on
the Oracle and BEA site
You also need to install the Java Software Development Kit (JDK) 1.5 or later
on the computer that will run the command line tools. The JDK is at Sun
Developer Network
Database
For all application servers and platforms:
●
Oracle 10g (Standard and Enterprise Editions)
For JBoss on Windows:
●
Microsoft SQL Server 2005 SP1 (Enterprise Edition and Standard Edition)
For JBoss on Windows or Linux:
Database driver
●
MySQL 5.0.18 (InnoDB Engine)
●
SQL Server 2005 JDBC 1.1 - sqljdbc.jar
●
MySQL - mysql-connector-java-3.1.12-bin.jar (3.1.12)
●
Oracle 10g - ojdbc14.jar, Release 2 (10.2.0.2 Thin)
7
Adobe Flash Media Rights Management Server
System Requirements
Installing and Deploying Adobe Flash Media Rights Management Server
Web browser support
8
Web browser support
This table outlines the supported web browsers for the Flash Media Rights Management Server
administrator user interface, which is LiveCycle Administration Console.
Operating system
Supported browser
Microsoft Windows Vista™
Internet Explorer 7 or later(1)(2)
Firefox 2.0.0.1 or later(1)
Windows 2000
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
Internet Explorer 6 or later(1)(2)
Firefox 2.0.0.1 or later(1)
Windows Server 2003
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x (Intel)
Firefox 2.0.0.1 or later(1)
(1)“or later” includes major revisions. For example, Microsoft Internet Explorer 6.0 or later also covers
Microsoft Internet Explorer 7.0
(2)When using Internet Explorer on Microsoft Windows Vista or Windows XP, the Use SSL 3.0 option in
Internet Explorer must be selected. Otherwise, you cannot play encrypted FLV files.
Additional requirements for Linux operating systems
The installer for Adobe LiveCycle ES (Enterprise Suite) Update 1 (8.2) requires the GNU bc utility (an
arbitrary precision calculator language) to be available on the Linux system. Usually, this utility is present
by default. Ensure that it is installed on the system before you run the installer. If the utility is not present,
you will encounter error messages that warn you about the lack of disk space because the bc utility is used
to compute whether enough disk space is available before you start the installation. The bc utility may be
provided by your operating system vendor; otherwise, you can get it at the GNU Operating System site.
Note: To verify that the utility is available, execute which bc from the shell. If the utility is available, the
path to the program is displayed.
Installing from network drives
It is recommended that you install Flash Media Rights Management Server only from the installation
media or a local disk drive. Attempting to install the software over a network causes considerable delays in
launching and installing.
Adobe Flash Media Rights Management Server
System Requirements
Installing and Deploying Adobe Flash Media Rights Management Server
Installing on a cluster
9
Installing on a cluster
If you intend to install and deploy Flash Media Rights Management Server in a clustered environment,
follow the preparatory and installation tasks outlined in Configuring LiveCycle ES Application Server Clusters
Using JBoss or Configuring LiveCycle ES Application Server Clusters Using WebLogic.
Configuration worksheet
It is recommended that you record the following information and keep it conveniently accessible for
future use. This information will be required during the installation and configuration process, and is also
important for activities such as patching and upgrades.
Tip: Print this page to keep note of your settings as you progress through this document.
Component
Information
Value
Application server
Computer IP address or fully
qualified domain (see note
below)
enter value here
Database
Host name or IP address
enter value here
Database
Port number
enter value here
Database
Service ID
enter value here
Database
Database name
enter value here
Database
User name and password
enter value here
JDK
Install path [JAVA_HOME]
enter value here
Application server
Install path [appserver root]
enter value here
Application server
User name & password
enter value here
Application server
Port number
enter value here
WebLogic Server
Managed server name and
path
enter value here
Rights Management Server
Serial number
enter value here
Rights Management Server
Install path [FMRMS root]
enter value here
Rights Management Server
Certificate expiry date
enter value here
LiveCycle ES
Install path [LiveCycleES root]
enter value here
POP3.jar file
Location
enter value here
LiveCycle Administration Console
Administrator name and
password
enter value here
Note: Use of [localhost] during configuration causes errors. Use the application server’s IP address or fully
qualified domain for all instances.
2
Installing Flash Media Rights Management Server
Flash Media Rights Management Server requires the installation of LiveCycle ES Update 1 and LiveCycle ES
Update 1 Service Pack 1. You should install the LiveCycle ES components on a new server instance.
Complete the following installation tasks in the order shown:
1. Ensure that your server environment conforms with the system requirements. (See “System
Requirements” on page 6.)
2. Install LiveCycle ES Update 1. (See “Installing LiveCycle ES Update 1” on page 10.)
3. Install LiveCycle ES Update 1 Service Pack 1. (See “Installing LiveCycle ES Update 1 Service Pack 1” on
page 11.)
4. Install Flash Media Rights Management Server. (See “Installing Flash Media
Rights Management Server” on page 11.)
5. When you finish installing Flash Media Rights Management Server, configure SSL and other settings.
(See “Post-Deployment Tasks” on page 12.)
6. Obtain a certificate from Adobe, based on your server name so that you can create policies and
package content.
Installing LiveCycle ES Update 1
Before you install Flash Media Rights Management Server, you must install LiveCycle ES Update 1, which is
available in the LiveCycleES_8.2.1 folder of the Flash Media Rights Management Server DVD. Refer to the
LiveCycle ES documentation listed below for details about how to perform the installation:
●
To install and deploy LiveCycle ES using Turnkey, see Installing and Deploying LiveCycle ES Using Turnkey.
●
To install and deploy LiveCycle ES on a single server, first follow the instructions in Preparing to Install
LiveCycle ES (Single Server). If you are installing on JBoss, be sure to perform the procedure named “To
enable Watched Folder invocations”. This procedure enables user event logging. Next, follow the
instructions in Installing and Deploying LiveCycle ES for JBoss or Installing and Deploying LiveCycle ES for
WebLogic.
●
To install and deploy LiveCycle ES on server clusters, first follow the instructions in Preparing to Install
LiveCycle ES (Server Cluster). Next, follow the instructions in Configuring LiveCycle ES Application Server
Clusters Using JBoss or Configuring LiveCycle ES Application Server Clusters Using WebLogic.
●
To upgrade to LiveCycle ES 8.2 from LiveCycle 8.0.x, first follow the instructions in Preparing to Upgrade
to LiveCycle ES from 8.0.x. Next, follow the instructions in Upgrading to LiveCycle ES 8.2 from 8.0.x for JBoss
Turnkey, Upgrading to LiveCycle ES 8.2 from 8.0.x for JBoss, or Upgrading to LiveCycle ES 8.2 from 8.0.x for
WebLogic.
Note: Do not run LiveCycle Configuration Manager after you install LiveCycle ES Update 1. You must install
the service pack first.
10
Adobe Flash Media Rights Management Server
Installing and Deploying Adobe Flash Media Rights Management Server
Installing Flash Media Rights Management Server
Installing LiveCycle ES Update 1 Service Pack 1
Installing LiveCycle ES Update 1 Service Pack 1
After you install LiveCycle ES Update 1, install the service pack by following the instructions in Adobe
LiveCycle ES Update 1 Install Instructions and Fixed Customer Issues, which is available at
http://help.adobe.com/en_US/fmrms/1.5/8.2.1_sp1_readme.pdf. The service pack is available in the
LiveCycleES_8.2.1_SP1 folder of the Flash Media Rights Management Server DVD.
After you complete the installation, run LiveCycle Configuration Manager.
Installing Flash Media Rights Management Server
Next, install Flash Media Rights Management Server.
➤ To install Flash Media Rights Management Server:
1. Create a folder named FMRMS1.5 on the computer where you want to install Flash Media
Rights Management Server:
●
(Windows) C:\Adobe\FMRMS1.5\
●
(Linux) /opt/adobe/fmrms1.5/
2. Copy the contents of the fmrms_tools and sdk folders from the DVD into the folder that you created.
11
3
Post-Deployment Tasks
This section provides information about configuring SSL and other settings, as well as other information
that is required to get started using Flash Media Rights Management Server:
●
“Configuring SSL” on page 12
●
“Configuring Flash Media Rights Management Server” on page 12
●
“Configuring the credentials” on page 15
●
“External authenticators and authorizers” on page 16
●
“Flash Media Rights Management Server tools” on page 16
●
“Uninstalling LiveCycle ES” on page 16
Configuring SSL
As a security product, Flash Media Rights Management Server requires the configuration of Secure
Sockets Layer (SSL) when running on a production system. SSL is optional only when running Flash Media
Rights Management Server on an evaluation system. For instructions about how to configure SSL for
JBoss Application Server or WebLogic Server, see "Configuring SSL" in Administering LiveCycle ES.
Configuring Flash Media Rights Management Server
This section describes the tasks that are required to configure the Flash Media Rights Management Server
settings:
●
“Modifying the config.xml file” on page 12
●
“Creating the Packager User” on page 14
Caution: Do not modify Flash Media Rights Management Server in any way other than the configurations
that are described in this section. Modifying your server environment can cause critical issues.
Modifying the config.xml file
Modify the config.xml file to set the base URL, enable web service, customize user prompts, and add
support for private keys. If you want to enable multiple tenant support, see “Configuring the server for
multiple tenant support” on page 13 before you perform the following procedure.
➤ To modify the config.xml file:
1. In LiveCycle Administration Console, click Services > LiveCycle Rights Management ES >
Configuration > Manual Configuration.
2. Click Export to get the existing configuration file and save the config.xml file to another location.
3. In a text editor, open the config.xml file and make the following changes:
●
Locate the "WebServiceEnabled" property and change the value to "true".
12
Adobe Flash Media Rights Management Server
Installing and Deploying Adobe Flash Media Rights Management Server
●
Post-Deployment Tasks
Modifying the config.xml file
13
Locate the "CustomHeadingPrompt" property and change the value to an appropriate display
message for your end users when they access Adobe Media Player.
The next part of the task is to add the configuration that enables signing LiveCycle ES vouchers for your
Flash Media Rights Management Server.
4. With the config.xml file still open, navigate to the config directory, either on the DVD or in the
[FMRMS root] directory, and locate the DRM_Section.xml file.
5. In a text editor, open the DRM_Section.xml file, copy the contents and paste them into the open
config.xml file within the PolicyServer node, immediately after these lines:
<node name="Policy Server">
<map/>
Note: This node may not appear in the same location if you export the config.xml file again because
LiveCycle ES may reorder the nodes.
6. In the DRM > SignatureCredentials node, set the entry key to a secure connection (that is,
https) that contains either the full server name or the IP address (localhost is not acceptable in this
instance) and the port number that was specified when configuring SSL for your application server (as
shown in these examples):
●
(JBoss) https://[RightsManagementServer].[MyOrganization].com:8443)
●
(WebLogic) https://[RightsManagementServer].[MyOrganization].com:7002)
This base URL is embedded in policy-protected files and is used by client applications to connect back
to the server. Secured files will continue to contain the base URL, even if it is changed later. If you
change the base URL, configuration information must be updated for all connecting clients. Also, the
base URL is case-sensitive and must match the server URL.
7. Save and close the config.xml file.
8. Navigate to the Manual Configuration page in LiveCycle Administration Console, browse to the
config.xml file that you just modified, and click Import to import it.
9. Click OK.
Configuring the server for multiple tenant support
By default, Flash Media Rights Management Server supports a single credential for voucher signing. You
can also enabled multiple tenant support, which allows a single LiveCycle ES server or server cluster to
supply licenses for multiple content publishers. You can configure a separate URL for each publisher, and
then clients can then use one of the URLs to request a voucher.
Keep the following notes in mind:
●
Any minimum client version enforcements made by the server affect all tenants. DRM version keys are
configurable for a server but are not configurable for each tenant.
●
A single SAML assertion duration is set for all tenants.
●
CustomHeadingPrompt, CustomUsernamePrompt, CustomPasswordPrompt items, which are
displayed by Adobe Media Player, are shared access all tenants.
●
When using multiple tenant support, each tenant's URL must have a different host name.
Adobe Flash Media Rights Management Server
Installing and Deploying Adobe Flash Media Rights Management Server
Post-Deployment Tasks
Creating the Packager User
14
➤ To enable multiple tenant support:
1. In LiveCycle Administration Console, click Services > LiveCycle Rights Management ES >
Configuration > Manual Configuration.
2. Click Export to get the existing configuration file and save the config.xml file to another location.
3. In a text editor, open the config.xml file.
4. In the DRM > SignatureCredentials node, add entries that associate a URL with a credential alias,
as shown in bold in the following example:
<node name="DRM">
<map>
<entry key="AllowUnencryptedVoucher" value="true"/>
</map>
<node name="SignatureCredentials">
<map>
<entry key=”https://publisher1.fmrms.com:8443”
value=”PUBLISHER1_CREDENTIALS”/>
<entry key=”https://publisher2.fmrms.com”
value=”PUBLISHER2_CREDENTIALS”/>
</map>
</node>
<node name="VersionKeys">
...
</node>
5. Save and close the config.xml file.
6. Navigate to the Manual Configuration page in LiveCycle Administration Console, browse to the
config.xml file that you just modified, and click Import to import it.
7. Click OK.
Creating the Packager User
Create and configure the Packager User in User Management. This user will be the authorized user for the
Flash Media Rights Management Server command line tools.
Tip: The successful creation of a new user confirms that your LiveCycle ES server is properly configured
and communicating with your application and database servers.
➤ To create the Packager User:
1. In LiveCycle Administration Console, click Settings > User Management > Users and Groups, and
then click New User.
2. Enter the required information into the appropriate boxes (names are marked with an *), and click
Next.
3. On the Add User to Groups page, click Next. A user group is not required.
4. On the Assign Roles to User page, click Find Roles.
Adobe Flash Media Rights Management Server
Installing and Deploying Adobe Flash Media Rights Management Server
Post-Deployment Tasks
Configuring the credentials
15
5. In the roles list, select the following roles to assign, and then click OK.
●
Application Administrator
●
Services User
Caution: Do not select Super Administrator for this user because it deactivates critical permissions.
6. Click Finish to save the new user.
Configuring the credentials
This section describes the steps that are required to import and configure the Rights Management Server
certificate (PFX) file that you obtained from Adobe. For information about obtaining a credential, contact
your Adobe representative. You need to provide your server’s name when obtaining the credential. The
server name must match the URL that you set in the config.xml file. (See “Modifying the config.xml file” on
page 12.)
➤ To import the certificate:
1. In LiveCycle Administration Console, click Settings > Trust Store Management > Local Credentials.
2. Click Import and, under Trust Store Type, select Document Signing Credential.
3. In the Alias box, type the identifier for the credential. This identifier is used as the display name for the
credential in Flash Media Rights Management Server. It is also used to access the credential
programmatically by using the LiveCycle ES SDK.
Note: The alias name must be the same as the entry’s value in the SignatureCredentials node in
the config.xml file. In the sample DRM_Section.xml file, it is called FLV HEADER AND VOUCHER
SIGNING. The alias name is automatically converted to uppercase for display purposes but is
not case-sensitive when you refer to it in a process.
4. Click Browse, locate the credential, and then click Open.
5. In the Password box, type the password that is associated with the credential and then click OK.
Replacing expired credentials
If you are updating or replacing an expired credential with a new valid credential, restart the LiveCycle ES
server after the update. You cannot download a new voucher until you restart the LiveCycle ES server
because the older expired credential is cached.
Switching from temporary to permanent credentials
If you have been evaluating Flash Media Rights Management Server by using a temporary
Rights Management Server certificate (PFX) file and have received a new permanent Flash Media
Rights Management Server credential, complete the following procedure to replace the old credential.
Note: Any media that is packaged with the old credentials will have to be repackaged with the new ones.
Adobe Flash Media Rights Management Server
Installing and Deploying Adobe Flash Media Rights Management Server
Post-Deployment Tasks
External authenticators and authorizers
16
➤ To switch from temporary to permanent credentials:
1. Log in to LiveCycle Administration Console and click Settings > Trust Store Management > Local
Credentials.
2. Make a note of the name of the old credential and then delete it.
3. Import the new credential using the same name as the old credential.
4. Restart the LiveCycle ES server to clear the old credential from the cache.
External authenticators and authorizers
Before you can prepare your media content for publication, you must install an external authorization
handler that will provide centralized access control for FLV files in your organization. Flash Media
Rights Management Server controls access to policy-protected FLV files by evaluating the policy when a
user attempts to access a policy-protected file. For information about deploying an authorizer, see
Developing Service Providers. For evaluation purposes, you can choose to use the sample authorizer (in
[FMRMS root]/SDK/samples).
To evaluate Flash Media Rights Management Server without setting up an external authenticator, you can
configure a local domain and add local users, as described in User Management Help. You can then use the
name of the local domain in your policies.
Flash Media Rights Management Server tools
Flash Media Rights Management Server installs with a suite of tools that are used to prepare the media
content for viewing in Adobe AIR applications, such as Adobe Media Player.
Before you can test protected content in an Adobe AIR application, you must create a policy and package.
(See Securing Video Content.)
Uninstalling LiveCycle ES
For instructions about how to uninstall LiveCycle ES, see "Uninstalling LiveCycle ES" in the document you
used when you installed LiveCycle ES:
●
To uninstall a turnkey installation of LiveCycle ES, see Installing and Deploying LiveCycle ES Using
Turnkey.
●
To uninstall LiveCycle ES from a single server, see Installing and Deploying LiveCycle ES for JBoss or
Installing and Deploying LiveCycle ES for WebLogic.
●
To uninstall LiveCycle ES from server clusters, see Configuring LiveCycle ES Application Server Clusters
Using JBoss or Configuring LiveCycle ES Application Server Clusters Using WebLogic.
●
To uninstall an upgraded installation of LiveCycle ES see Upgrading to LiveCycle ES 8.2 from 8.0.x for JBoss
Turnkey, Upgrading to LiveCycle ES 8.2 from 8.0.x for JBoss, or Upgrading to LiveCycle ES 8.2 from 8.0.x for
WebLogic.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement