Global Object Security Policy

The Global Object Security Policy (GOSP) is a setting in the Adobe Reader, Acrobat and PDF-XChange apps that controls how cookies behave. The default setting is "enable global object security policy" which means that every time someone renames a file or moves a file to a different location, a different cookie is created each time.

The Adobe and PDF-XChange device cookies (also known as 'Tracking ID' in the User Activity Log) relate to the "PDF (Adobe) Limit" in your DRM Policy Settings:

Vitrium-End-Users-Support-Guide-What-is-GOSP

Since Vitrium's protected content relies on these cookies to track the number of 'devices' that a user opens the protected PDF on, it is STRONGLY recommended that end users disable this feature.

  • If your end user DOES NOT disable this feature
    Then, they will track multiple cookies (or tracking IDs) on their same computer and may reach their device limit unnecessarily, prompting a support call to your organization.
  • If your end user DOES disable this feature
    Then, the Adobe or PDF-XChange app will track a single device cookie (or tracking ID) on that machine and the user will not likely reach their device limit.

 

Disable GOSP in Adobe (PC)

Disabling the "global object security policy" does NO HARM to your user’s computer. It is simply a mechanism to create a single tracking ID (or cookie) on their computer, no different than how a browser session tracks cookies as well.

To disable this feature in Adobe on a PC:

  1. From the top menu bar, click Edit > Preferences.
  2. Under Categories, click JavaScript.
  3. Uncheck the field "Enable global object security policy" and ensure the "Enable Acrobat JavaScript" field is checked.
  4. Click OK.

 

 

Disable GOSP in Adobe (Mac)

Disabling the "global object security policy" does NO HARM to your user’s computer. It is simply a mechanism to create a single tracking ID (or cookie) on their computer, no different than how a browser session tracks cookies as well.

To disable this feature in Adobe on a Mac:

  1. From the top menu bar, click Acrobat Reader > Preferences.
  2. Under Categories, click JavaScript.
  3. Uncheck the field “Enable global object security policy" and ensure the "Enable Acrobat JavaScript" field is checked.
  4. Click OK.

 

 

Disable GOSP in PDF-XChange

Disabling the "global object security policy" does NO HARM to your user’s computer. It is simply a mechanism to create a single tracking ID (or cookie) on their computer, no different than how a browser session tracks cookies as well.

To disable this feature in PDF X-Change (on a PC only):

  1. From the top menu bar, click File > Preferences.
  2. Under Categories, click JavaScript.
  3. Uncheck the field: "Enable global object security policy".
  4. Click OK.

 

Disabling the "global object security policy" does NO HARM to your user’s computer. It is simply a mechanism to create a single tracking ID (or cookie) on their computer, no different than how a browser session tracks cookies as well.

To disable this feature in Adobe on a PC:

  1. From the top menu bar, click Edit > Preferences.
  2. Under Categories, click JavaScript.
  3. Uncheck the field "Enable global object security policy" and ensure the "Enable Acrobat JavaScript" field is checked.
  4. Click OK.

Vitrium-End-Users-Support-Guide-Steps-to-Disable-GOSP

 

Bluebeam Revu

 Bluebeam Revu does not have a "GOSP" setting. GOSP stands for Global Object Security Policy, which appears in Adobe Acrobat and PDF X-Change. However, if you encounter issues with Bluebeam Revu, you can follow the steps below o achieve the same effect by managing Bluebeam's JavaScript Web Services and Trust Center settings instead:

  1. Open Bluebeam Revu.
  2. Open the Preferences window by pressing Ctrl + K (or go to Revu > Preferences).
  3. Click on JavaScript tab near the top.
  4. Check that  Enable Acrobat JavaScript is active.
  5. End Users may need to add protectedpdf.com or your custom domain to the Trusted Hosts section as well.
    1. Click on the Trusted Hosts tab near the centre.
    2. Click ADD.
    3. Enter the relevant domain.
    4. Click OK.
  6. Ensure you click OK in the bottom right to save the changes. Relaunch the app and try to open the Protected PFD again.