This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 135189 - Services tab shows "wrong admin user name" upon server refresh
Summary: Services tab shows "wrong admin user name" upon server refresh
Status: RESOLVED DUPLICATE of bug 149367
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P4 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-15 23:57 UTC by lpolycarpou
Modified: 2008-11-14 23:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
services-refreshnode (38.34 KB, image/jpeg)
2008-05-15 23:59 UTC, lpolycarpou 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2008-05-15 23:57:44 UTC 
When clicking refresh for a GlassFish V2 server in the Services tab (which is running remotely), the message "Wrong
admin user name or password. Refresh the node." appears under the server node which is entirely misleading.  The GF
server has correct credentials entered and does refresh itself correctly soon after.  This only shows up for remotely
managed domains.

See attached screenshot.
Comment 1 lpolycarpou 2008-05-15 23:59:36 UTC 
Created attachment 61455 [details]
services-refreshnode
Comment 2 lpolycarpou 2008-05-16 00:01:36 UTC 
Found in CAPS Sierra Early Access 3 build:

Product Version: NetBeans IDE 6.1 RC1 (Build 200804090901) - Java CAPS Enabled
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-b05
System: Windows Vista version 6.0 running on x86; Cp1252; en_GB (nb)
Comment 3 Jana Maleckova 2008-05-16 16:18:00 UTC 
reassign for webservices for evaluation
Comment 4 Lukas Jungmann 2008-07-22 22:26:51 UTC 
glassfish plugin issue, perhaps already fixed
Comment 5 Vince Kraemer 2008-08-27 01:43:34 UTC 
Changing this would be kind of tricky...

We would need to change the display name of the node.... based on the authentication results.
Comment 6 Vince Kraemer 2008-11-14 23:29:10 UTC 

*** This issue has been marked as a duplicate of 149367 ***