Follow

What is the Acrobat Global Object Security policy?

Adobe introduced the Global Security Policy in Acrobat 8.0 and enabled it out of the box. This setting will not allow a document to access an Acrobat cookie that was created by a different document. We currently store offline access and the computer id in Acrobat cookies. However, this may not be an issue depending on your business requirements. If you require pseudo single sign-on or offline document package single sign-on, then you need your users to disable this setting. If you require that moving the document around the local file system (or downloading multiple times in the browser cache) should not result in a new machine id, then you need your users to disable this setting. Otherwise, you don't need the user to do anything but you do need to alter the document behavior (see * below)

 

When using the Protectedpdf API/SDK, you have the ability to modify the document behavior with regards to the Global Security Policy. In the Document object, you'll see:

 

GlobalSecurityMessageMode GlobalSecurityMessageMode { get; set; }

where

enum GlobalSecurityMessageMode

{

   PromptAndCloseDocument = 0,

   PromptOnly = 1,

   NoPromptAndNoClose = 2

}

 

Having a default value of PromptAndCloseDocument.

  • PromptAndCloseDocument will prompt the user if they don't have the global security policy setting disabled and will close the document until they make this change.
  • PromptOnly will do the same but will not close the document.
  • NoPromptAndNoClose will neither prompt the user nor close the document (* this is the setting you would choose if none of the above-mentioned scenarios apply to your business requirements).

When using the protectedpdf.es Web admin site, you do not have the ability to modify the document behavior with regards to the Global Security Policy. Documents will always prompt and close.

Here are the steps for Users to change the Acrobat global security policy.

In Acrobat, go to the menu Edit -> Preferences -> JavaScript and deselect the "Enable global security policy" checkbox.

In Vitrium Security’s Web.Config, there are several settings that limit how much data could be transferred to the server.  You can increase the MaxRequestLength in the section below.  MaxRequestLength is in KB.

 

   <microsoft.web.services2>

      <diagnostics/>

      <messaging>

         <maxRequestLength>122880</maxRequestLength>

         <executionTimeout value="600"/>

      </messaging>

   </microsoft.web.services2>

 

You can also increase the maxAllowedContentLength in the section below.  maxAllowedContentLength Is in bytes. (IIS7 and 7.5)

 

      <security>

         <requestFiltering>

            <requestLimits maxAllowedContentLength="1000000000" />

         </requestFiltering>

      </security>

 

0 Comments

Please sign in to leave a comment.
Powered by Zendesk