134621 - Mozilla 0.9.9 (jre1.3.1) connecting to a HP Ethernet Switch requires the password numerous times

Status: RESOLVED DUPLICATE of bug 60304

(Core Graveyard :: Java: OJI, defect)

Description

[tammer]

Hello,
if I use Mozilla 0.9.9 build 2002033109 to connect to a HP Ethernet Switch
I have the problem that I must enter the password numerous times. Java did not
recognize the entered password and requests the password each time I load a new
page (in the same session, from the same URL).

The following errors shows up in the Java console. 
There is no proxy between this switch and my browser. 
The local domain is in the proxy exclusion list.

Exception occurred during event dispatching:

java.security.AccessControlException: access denied (java.lang.RuntimePermission
modifyThread)

	at java.security.AccessControlContext.checkPermission(Unknown Source)

	at java.security.AccessController.checkPermission(Unknown Source)

	at java.lang.SecurityManager.checkPermission(Unknown Source)

	at sun.applet.AppletSecurity.checkAccess(Unknown Source)

	at java.lang.Thread.checkAccess(Unknown Source)

	at java.lang.Thread.stop(Unknown Source)

	at PortGraph.removeToolTip(PortGraph.java)

	at PortGraph.mouseMove(PortGraph.java)

	at java.awt.Component.handleEvent(Unknown Source)

	at PortGraph.handleEvent(PortGraph.java)

	at java.awt.Component.postEvent(Unknown Source)

	at java.awt.Component.dispatchEventImpl(Unknown Source)

	at java.awt.Container.dispatchEventImpl(Unknown Source)

	at java.awt.Component.dispatchEvent(Unknown Source)

	at java.awt.EventQueue.dispatchEvent(Unknown Source)

	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

	at java.awt.EventDispatchThread.run(Unknown Source)

Exception occurred during event dispatching:

java.security.AccessControlException: access denied (java.lang.RuntimePermission
modifyThread)

	at java.security.AccessControlContext.checkPermission(Unknown Source)

	at java.security.AccessController.checkPermission(Unknown Source)

	at java.lang.SecurityManager.checkPermission(Unknown Source)

	at sun.applet.AppletSecurity.checkAccess(Unknown Source)

	at java.lang.Thread.checkAccess(Unknown Source)

	at java.lang.Thread.stop(Unknown Source)

	at PortGraph.removeToolTip(PortGraph.java)

	at PortGraph.mouseMove(PortGraph.java)

	at java.awt.Component.handleEvent(Unknown Source)

	at PortGraph.handleEvent(PortGraph.java)

	at java.awt.Component.postEvent(Unknown Source)

	at java.awt.Component.dispatchEventImpl(Unknown Source)

	at java.awt.Container.dispatchEventImpl(Unknown Source)

	at java.awt.Component.dispatchEvent(Unknown Source)

	at java.awt.EventQueue.dispatchEvent(Unknown Source)

	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)

	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

	at java.awt.EventDispatchThread.run(Unknown Source)


Bye
  Rainer Tammer

Comment 1

[timeless]

have you tried to use nc4 w/ the same jre

Comment 2

[tammer]

Netscape 4.x and IE 5.5, 6.0 are working without a problem.
bye
  rainer

Comment 3

[tammer]

Hello,
I also tested Opera 6.x with Java 1.3.1 ... and its working.
bye
  rainer

Comment 4

[Olivier Cahagne]

Reassigning to OJI component.

Comment 5

[Tony Tovar]

I see the same(?) problem with build 2002-04-01(06) on WinNT and JRE 1.4.0.

I have several different HP hubs.  I tested it on my 2524 and 2424 switches. 
For both, I had to login via the browser to access the config screens (which is
normal).  Then, when I actually tried to change something, the JRE prompted me
for the login.  I don't remember if this is expected or not.  

Is Mozilla supposed to be passing this login to the JRE?

Also, I suggest clarifying the summary, e.g. "Java requests duplicate password
login."

Comment 6

[Matthias Versen [:Matti]]

*** This bug has been marked as a duplicate of 60304 ***

Comment 7

[R.B.]

I am not sure that all these bugs are the same. The error in Java console of the
original reporter can usually be avoided by setting the appropriate Java policy,
in this case by putting:

grant {
  permission java.lang.RuntimePermission "modifyThread";
};

(or similar) in a file .java.policy in user's home directory, if using Linux.
Not sure about Windows, and what the general security implications are.