Server Configuration - Adobe 12001196 - Acrobat - Mac Manual

Application Security Guide
5. Save and close the policy file.
Typical allow-access-from-identity block
<allow-access-from-identity>
<signatory>
<certificate
fingerprint="01:23:45:67:89:ab:cd:ef:01:23:45:67:89:ab:cd:ef:01:23:45:67"
fingerprint-algorithm="sha-1"/>
</signatory>
</allow-access-from-identity>
7.3.4 Fingerprint usage rules
• Multiple signatories require multiple <allow-access-from-identity> blocks.
• There must be one and only one <signatory> block inside an
<allow-access-from-identity>.
• Only <certificate> is allowed inside a <signatory>. Since <public-key> is not supported
for 9.1, <public-key> blocks encountered are skipped.
• The fingerprint attribute is required. If it is missing or malformed, the certificate block is
skipped. The string must be 40 characters long not counting spaces or colons.
• The fingerprint-algorithm attribute is required. If it is missing or malformed, the certificate
block is skipped. The string is case insensitive.

7.4 Server configuration

Policy files function only on servers that communicate over HTTP, HTTPS, or FTP.
7.4.1 Policy file host basics
When creating and using a policy file, the following rules apply:
• It's name must be crossdomain.xml.
• The file MIME type should be set to
• 9.2/8.17: text/x-cross-domain-policy
• 9.3/8.2: Any type supported by the specification.
• The file usually resides at the server's root. However, a master policy file can point to policies in
other locations. While a "root" is defined differently by each server, it is always true that you should
be able to enter the following in a browser to see the file:
http(s)://myserverroot.com/crossdomain.xml
• Non-master policies permit access only to files at or beneath their level in the directory tree. You can
avoid the master policy requirement by calling the policy via JavaScript. See
Calling policies via JavaScript.
7.4.2 Differences between Acrobat and Flash
The Acrobat family of products leverages the Flash model. However, there are differences.
Section 7 Cross Domain Configuration
Section 7 Cross Domain Configuration
Page 63