The Global Object Security (GOS) policy is a setting in Adobe Reader and Adobe Acrobat that controls how cookies in Adobe products behave. The default setting is to "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. Since Vitrium Security's content security solution relies on these cookies to track the number of 'devices' that a user opens the secured content on, it is STRONGLY recommended that end users disable this feature.
Users will only need to do this once for one computer. If they wish to open the protected PDF file on a 2nd computer (assuming they have permission to do so), then they will need to disable the GOS policy in Adobe on the other computer as well.
To learn more about disabling the GOS check out the 'How to Support Your End-Users' guide.
Why do users need to disable the Global Object Security Policy in Adobe?
Because otherwise the user may exceed the limit that was set for them in their DRM policy and they will encounter the vc3 error message (You have exceeded your PDF or browser limit) even if they have only opened the file on the same computer.
By disabling Adobe's GOS policy, the user can then safely move the protected file from one folder to another, or rename the protected file to something else, but not reach their limit as the cookie is saved with the file on that same computer.
Can I remove the Adobe global object security policy pop-up message?
Yes, you can remove this message but we only recommend this to Vitrium customers who DO NOT set a PDF limit in their DRM policy settings.
To remove the message on a new content setting:
This can also be done in an existing document content setting as long as the content setting has not been applied to more than 25 files. If it has been applied to more than 25 files, feel free to reach out to email@example.com to get the change made for you.
Using Vitrium Security's VersionUnique API, this content setting can be changed/overridden by including this parameter:
AcroJsGosBehaviourType would apply to Acrobat v10 and earlier releases
AcroJsGosUnlimitedBehaviourType would apply to Acrobat v11 and newer releases
Definition of each Acrobat GOS policy setting:
For the secured web documents to work offline, a copy needs to be saved in the user's browser cache. This is a quick video shows how you can save a copy on your browser cache for offline use of the secured web document (Vitrium's Web Viewer):
Basically, the web document needs to be saved in the browser’s cache (as cookies) so it can be used later when the User decides to access it ‘offline.’ You’ll notice in the video also the delete button to remove this ‘saved copy’ from the browser for when their use is done.
We highly advise for the User to clean up their browser cache soon after they’re done reading the document offline as it will eventually fill up their browser caching storage (which gets stored on the hard drive). Simply put, if they save all the documents they have permission to for offline use, the browser cache can get quite large and it will start to slow down their computer speed for processing things.
Here’s an article online that you can read for more clarification on the browser cache: http://www.makeuseof.com/tag/browser-cache-makeuseof-explains/
We recommend that you initially set up your Users (the recipients of your content) with a strong password, minimum 8 characters, and one that uses a combination of letters, numbers, and special characters.
We also recommend you select "Force user to change password" when you're adding Users into your Vitrium account as this way, the User can select their own password which may be more familiar to them.
For additional password controls, be sure to read more about our "Security Settings" in the Vitrium Security Admin Manual.
Offline days, when greater than 0, allows Web Viewer users to click the toolbar icon "Save to Browser" and save that content to the browser's cache and be offline -- no Internet access -- for those number of days. The user would also have to bookmark the Web Viewer URL in order to access that content offline. Once the number of days lapses, if the user is online, they will automatically be authenticated once again and be granted another (N) days offline. If the user is offline, the content will be locked and the user logged out. The user will need to be online and log in once again to continue to access the content. This re-authentication forces the Webviewer content to communicate back with Vitrium’s server to re-validate the User’s authenticity while checking if the content and/or DRM policy is still valid.
Expiry date is when content is set to expire, depending on the level the DRM Policy is set, it renders all access for the User(s) or Group(s) to be denied when the date comes. This is determined by setting a specific date of expiry.
Thus, the most predominant difference is that Offline days used for those users who can’t connect to the internet and this feature enables them to have access to the protected content without an internet connection. On the other hand, Expiry dates limits user(s) or group(s) from accessing the content after the date you’ve set. Subscription-based businesses can benefit from the Expiry date feature and also expiry after first unlock.
NOTE: If Expiry date is set, offline days will be shortened if it allows the user to go beyond the expiry date.