Issue 21324

Product Requirement 
OOo should allow to restrict the level of access that components and scripts
have. The configuration granularity has to at least distinguish between a
document only, file, network or no access/execution. If some code tries to do an
action that is not permitted a prescriptive error message should be shown that
explains why the code could not be executed and what configuration options
prevented the action.

Customer Need/Problem
Administrators and users want to configure what resources (network, operating
system, etc.) a user can programmatically access.


Product Concept
Authorization ? Control what scripts and components are allowed to do when
running [High Cost, High Risk]  Need to control not just what scripts are run,
but what they can do when they are running. To do this you must ensure all
scripts are run with a suitable security context that will restrict OOo
application API calls, UNO API calls and Java API calls, according to the
security profile settings for the script source. At the minute both UNO and Java
are bootstrapped with an appropriate security context, but the OOo application
APIs are not making any security checks against UNO before they make any
security sensitive calls. These security checks will need to be implemented for
all of the applications and is a considerable amount of work.