1 HOME


© 2013 Adobe Systems, Inc. All rights reserved.

Updated Nov 11, 2014.

4   Custom Signature Appearances

Personalized signature appearances allow you to provide additional information about yourself, affiliations, or company. Home users often modify the default appearance as a matter of personal taste, while enterprise users are sometimes provided with a company-specific style and logo. All appearance data is stored in the appearances.acrodata file at %USER%\Application Data\Adobe\Acrobat\(version)\Security.

Every aspect of the visible appearance is subject to customization, and the options range from using logos, a replica of your handwritten signature, photos, images, and text. A typical appearance consists of three customizable components:

_images/appearance_sample6.png

You can create any number of appearances ahead of time for later use, and the signing workflow allows you to select one from your library of appearances. However, you can also select the default appearance created from your name or create one on-the-fly at signing time. </

_images/appearance_sample1.png

When you sign a PDF file, the appearance becomes part of the signed document. It is not part of the signature.

_images/appearance_sample2.png

4.1   Technical Details for Admins

Some data needed digital signature workflows is stored in .acrodata files. This is true for signature appearances, and the appearances.acrodata file is one of four such files:

  • appearances.acrodata: Stores signature appearances. Unless there is a shared company appearance, do not use this file.
  • addressbook.acrodata: Populates the Trusted Identity Manager with certificate data. This file can be used to distribute a trust anchor for signature validation.
  • directories.acrodata: Populates the directory server list in the Security Settings Console. This file can be used to configure connections to an LDAP server used as a certificate repository.
  • security-policy.acrodata: Populates the security policy list in the Security Policy Manager. This file can be used to distribute common document security policies.

The exact path to these files vary by application, version, platform, and user. For example:

  • Windows: C:\Documents and Settings\(user name)\Application Data\Adobe\Acrobat\(version)\Security
  • Windows 7/Vista: C:\Users\(user name)\AppData\Roaming\Adobe\Acrobat\(version)\Security
  • Macintosh: /Users/(user name)/Library/Application Support\Adobe/Acrobat/(version)/Security

4.1.1   What is an acrodata file?

An acrodata file is a PDF file. Like any PDF file it’s composed of a header, a bunch of objects that contain stings and streams (in this case the streams are the appearance images), a cross reference table, and a trailer. If you change the extension to PDF and open the file in Acrobat you’ll see each custom image on its own page, but all you’ll see are the pictures. By using a text editor, you can see the other things that help define the custom signature appearance. You’ll see things like <Reason true> <Location false> and all of the other bits and pieces that define the appearance.

The file is loaded when it’s needed rather than on launch. Those time include when user invokes the New(or Edit) signature appearances panel under Preferences and when the Sign Document dialog is called. It’s at that time that the PPKlite plug-in looks in the user’s Security folder for the file, and if it’s there, loads the appearance list so the user can select one to edit or apply.

At signing time, the signature appearance is written into the PDF file and saved so that it gets signed along with all of the previously existing data. If you’ve chosen a custom appearance, that object was copied from the acrodata file and used to help create the signature object in the signed PDF file.

For details about deploying custom appearance files for your enterprise, see www.adobe.com/go/acrobatwizard.

4.2   Customizing an Appearance

Users generally customize one or more signature appearances and store them for later use. Available signatures are listed in the appearance panel at signing time.

To customize a new signature appearance:

  1. Choose Edit > Preferences (Windows) or Acrobat > Preferences (Macintosh).

  2. Choose in the left-hand list:

    • 10.x and earlier: Security and in the Appearance panel, choose New or Edit.
    • 11.x: Signatures > Creation and Appearance > More, and in the Appearance panel, choose New or Edit.
_images/digsig_newappearance.gif
  1. Configure the signature appearance Title: Any title used to identify the appearance. These are useful for identifying which appearance to use for particular workflows.
_images/digsig_newappearance_title.png
  1. Set the graphic options in the Configure Graphic panel:

    • No graphic: No graphic is used.
    • Imported graphic: Choose File > Browse, select a file and choose OK.
    • Name: Your text extracted from the signing certificate.
_images/digsig_newappearance_graphic.png
  1. Set the text fields to display in the appearance in the Configure Text panel:

    • Name: The name associated with the certificate.
    • Date: The date signed. Signature appearances can only display local (computer) time, and it will likely differ from that in the Date/Time tab on the Signature Properties dialog when a timestamp server is used.
    • Location: The location associated with the identity configured in Acrobat.
    • Reason: The reason for signing.
    • Distinguished name: A name with details such as country, organization, organizational unit, and so on.
    • Labels: A label for each of the items above. For example, Reason.
_images/digsig_newappearance_textfields.png
  1. Logo: The logo or graphic used as a background watermark. The default watermark is the Adobe PDF logo. Your watermark will be shared automatically in all of your signature appearances.
_images/digsig_newappearance_logo.png
  1. Set the text direction and character set in the Text Properties panel:

    • Text Direction: Choose a direction appropriate for the signer’s language.
    • Digits: If languages are installed that use digits other than 1234567890, the drop-down list will be populated with alternate choices. Choose a digit set appropriate for the signer’s language.
  2. Choose OK.

_images/digsig_newappearance_textprops.png

4.3   Changing the Watermark

A watermark is a partially transparent graphic that appears “behind” a signature. By default, the watermark is the Adobe PDF logo. Line (vector) art that is simple and unobtrusive often works best.

  1. Import a logo or create a new one in a program such as Adobe Illustrator.

  2. Illustrator instructions: Set a low transparency level and flatten the transparency:

    1. Select all and group the objects if there is more than one.
    2. Choose Window > Transparency and move the slider to some low value such as 20%.
    3. Choose Object > Flatten Transparency. Leaving the Raster/Vector balance at 100%.
    4. Save the file as a PDF.
  3. Open the PDF file in Acrobat.

  4. Crop the page and remove white space (The method varies across product versions).

  5. Save the file as SignatureLogo.pdf in:

    • Windows: C:\Documents and Settings\(user name)\Application Data\Adobe\Acrobat\(version)\Security
    • Windows 7/Vista: C:\Users\(user name)\AppData\Roaming\Adobe\Acrobat\(version)\Security
    • Macintosh: /Users/(user name)/Library/Application Support\Adobe/Acrobat/(version)/Security

4.4   Using Handwritten Signatures

You can use your handwritten signature as the graphic displayed by your signature appearance as follows:

  1. Scan your signature at a relatively high DPI; for example, 300.
  2. Convert the image to vector drawing.
  3. Make the background transparent.
  4. Save the image in the desired format. A wide variety of formats is supported.
_images/appearance_sample3.png

4.5   PDF/A compliance

PDF/A is a subset of PDF intended as a file format suitable for the long-term archiving of electronic documents. Appearances in PDF/A-compliant documents must be must conform to the following:

  • Embed fonts. PDF/A requires font embedding because font metrics and glyph compliments change over time. Long term archiving can not rely on anything not included in the document.
  • Colors should use DeviceRGB when signing RGB/Office docs or else with associated ICC profiles.