United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6828964 non-admin users are unable to switch between new and old java plugin
JDK-6828964 : non-admin users are unable to switch between new and old java plugin

Details
Type:
Bug
Submit Date:
2009-04-10
Status:
Resolved
Updated Date:
2013-05-22
Project Name:
JDK
Resolved Date:
2013-05-22
Component:
deploy
OS:
windows_vista,windows_xp
Sub-Component:
plugin
CPU:
x86
Priority:
P3
Resolution:
Won't Fix
Affected Versions:
6u10,6u19
Fixed Versions:
6-pool

Related Reports

Sub Tasks

Description
http://forums.java.net/jive/thread.jspa?threadID=54600&tstart=0

From the above forum thread, some developers need to be able to switch between old and new java plugin via the Java Control Panel running as standard users.

The problem is due to currently the info. regarding using new java plugin is being stored in the HKLM branch of the registry which requires admin. privilege in order to modify it. We may need to store the same info. in the HKCU branch.
Not only can non-admin users switch between the new and the old java plugin on Windows XP, but it also seems that the administrator can't change the settings for regular users.

The plugin setting by an administrator does not affect browser's behavior in a standard users's environment. This is then compounded by the fact that a standard user cannot configure his/her own plugin setting on Windows XP.

We have a situation where regular users on Windows XP are not able to use the classic plugin because there is no way to disable/change their settings to do so. They always end up using the Next Gen Plugin - which is not acceptable in this customer's situation.

                                    
                                
http://forums.java.net/jive/thread.jspa?threadID=54600&tstart=0

From the above forum thread, some developers need to be able to switch between old and new java plugin via the Java Control Panel running as standard users.

The problem is due to currently the info. regarding using new java plugin is being stored in the HKLM branch of the registry which requires admin. privilege in order to modify it. We may need to store the same info. in the HKCU branch.
Not only can non-admin users switch between the new and the old java plugin on Windows XP, but it also seems that the administrator can't change the settings for regular users.

The plugin setting by an administrator does not affect browser's behavior in a standard users's environment. This is then compounded by the fact that a standard user cannot configure his/her own plugin setting on Windows XP.

We have a situation where regular users on Windows XP are not able to use the classic plugin because there is no way to disable/change their settings to do so. They always end up using the Next Gen Plugin - which is not acceptable in this customer's situation.

                                    

Comments
EVALUATION

Description section shows two problems:
Problem #1 - non admin user can't change new/old plugin setting via Java control panel
Problem #2- Admin user is able to change new/old plugin setting only for himself. In other words -
if admin changes new/old plugin setting via Java control panel then the change
does not affect browser's behavior in a standard users's environment.

Root cause of problem #2 is extracted as a CR 6953625:
For more information please also see "Suggested Fix" section of CR 6929996

Regarding problem #1 we need to decide how to change the current design
to use a different registry key to distinguish between new and old plugin setting.
Currently  Java distinguishes between new and old plugin setting using a registry key
[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in\1.6.0_xx]
which is allowed to be modified by admin only.
                                     
2010-05-24
This is a feature by design.
                                     
2013-05-22
EVALUATION

Description section shows two problems:
Problem #1 - non admin user can't change new/old plugin setting via Java control panel
Problem #2- Admin user is able to change new/old plugin setting only for himself. In other words -
if admin changes new/old plugin setting via Java control panel then the change
does not affect browser's behavior in a standard users's environment.

Root cause of problem #2 is extracted as a CR 6953625:
For more information please also see "Suggested Fix" section of CR 6929996

Regarding problem #1 we need to decide how to change the current design
to use a different registry key to distinguish between new and old plugin setting.
Currently  Java distinguishes between new and old plugin setting using a registry key
[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in\1.6.0_xx]
which is allowed to be modified by admin only.
                                     
2010-05-24
This is a feature by design.
                                     
2013-05-22



Hardware and Software, Engineered to Work Together