Issue 45894 - mozilla plugin requires "standard user" rights to be enabled
Summary: mozilla plugin requires "standard user" rights to be enabled
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-03-24 04:49 UTC by brant
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description brant 2005-03-24 04:49:14 UTC
The mozilla plugin requires administrator right to enable.

As administrator:
1. Install the 2.0 beta.
2. Copy the plugin to the Firefox plugin directory.
As limited user:
3. Open preferences for
4. Enable mozilla plugin.

Actual result:
Mozilla plugin is not enabled.  Checkmark for enabling plugin is not even

Expected result:
Plugin is enabled.

Do steps 3 and 4 as administrator.
Comment 1 Olaf Felka 2005-03-24 08:14:15 UTC
Comment 2 uwe.luebbers 2005-04-08 16:43:05 UTC
Hi Mikhail,

Even if you do it the right way (without copying), brantgurga is right.
The restricted user is not allowed to enable the mozilla plugin.
Comment 3 uwe.luebbers 2005-04-08 16:55:09 UTC
It only works if the admin who has installed Office enables the plugin. Then it works for 
all users.
Comment 4 mikhail.voytenko 2005-04-11 13:50:29 UTC
The problem is that the current plugin design uses windows system registry to
store the path to the OOo installation so that the plugin is able to find it.
This entry is written when user checks the entry. Without this entry the current
plugin implementation can not work. Thus a user with limited rights can not do it.
A possible fix would be to store this value during setup in to the system
registry and never remove it. The information whether the plugin should be used
might be stored in OOo registry as a boolean entry. In this case each user
should be able to activate or deactivate the plugin.
Comment 5 mikhail.voytenko 2005-04-11 14:29:03 UTC
Actually the mentioned above solution is more a workaround than a fix. And it is
not good for the final, since it is a complecated, error-prone change ( the
plugin will have to connect OOo constantly to check the boolean value ) in the
code that is not written by us.

And the most important thing is that the bug affects only "restricted users" who
can not change even local registry. "standard users" can do it. So I change the

The behaviour regarding restricted users is correct. They should use default
system settings selected by system administrator. The problem is that system
administrator can not preselect the behaviour of the mozilla plugin during setup
( the plugin is always deactivated after setup, so the administrator has to
start the office and access configuration menu to change the mozilla plugin
default settings ).

The clean solution would be to introduce an entry in the setup that would allow
a system administrator to set the default state of the mozilla plugin.
Comment 6 mikhail.voytenko 2005-04-11 15:41:14 UTC
So this bug now is only about introducing of a new "Mozilla plugin" entry into
the setup and I set the target to "OOo Later".
Comment 7 mikhail.voytenko 2005-04-11 15:53:06 UTC
Changing the priority to P3.
Comment 8 brant 2005-04-11 16:04:19 UTC
An alternative idea given that an administrator must install in
order for a limited user to use it and an administrator may change registry
permissions, the registry key required to be writable in order to activate the
plugin can be given Modify privilidges at installation time, though this
solution is less favorable from a security viewpoint.

I personally favor mav's first idea that that key which store the location of's installation be written at installation time.  In order to
enable the plugin, there would be a per-user boolean preference or possibly
since I think one can have per-user plugins, copying the plugin DLL to the
user's plugin directory to enable it.

By the way, if you know the registry key that needs modify privelidges, could
you add an entry to for 2.0?
Comment 9 mikhail.voytenko 2005-04-12 09:25:44 UTC
mav->brantgurga: The system administrator should not write the registry entry
himself. For now ( as workaround ) he should just do the steps 3 and 4 mentioned
by you and then the entry will be written.

Currently the feature is designed so that restricted user can not configure this
option. This is why the first solution suggested by me is not really a fix, it
will change the designed behaviour. If you whant it to be changed please submit
a standalone feature request for this.

The only wrong thing in current behaviour is that the system administrator has
to do steps 3 and 4 to let the mozilla plugin be activated by default. Instead a
system administrator should be able to specify whether the plugin should be
available by default during setup, the same way as it is done for OOo ActiveX
control and other components.
Comment 10 Marcus 2017-05-20 11:31:17 UTC
Reset assigne to the default "".