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 86331 - Need to stop PE plugin from asking for Username/Password intermittently (little frequently)
Summary: Need to stop PE plugin from asking for Username/Password intermittently (litt...
Status: RESOLVED DUPLICATE of bug 84932
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-02 19:47 UTC by Marco Walther
Modified: 2006-10-02 23:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Walther 2006-10-02 19:47:20 UTC
Sun Bug 6476820. I sent email about that before. I believe we see another case 
of the synchronization problems in the plugin.

VWP build 060927_9 on sparc - Binary NB 5.5 20060918 


I have seen this little dialog titled 'Sun Java System Application Server" 
asking for UserName and password showing up frequently -- while IDE startup, 
wile deploying, while restarting PE.

Need to configure this PE plugin to stop asking for this info.
attached screenshot.
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for 
context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) 
for context '/asadmin'
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for 
context ''
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) 
for context ''
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server 
[server] at [/__JWSappclients]
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
SEC5046: Audit: Authentication refused for [admin].
Web login failed: Login failed: javax.security.auth.login.LoginException: 
Failed file login for admin.
Comment 1 Vince Kraemer 2006-10-02 20:22:50 UTC
Many of the operation in the plugin need to communicate with the server.  That
communication must be authenticated with a correct username and password.

If the user enters an invalid u/p combo or presses the Cancel button the
communication with the server will fail.

We have added a better dialog in response to autherntication errors.  See issue
84932.

If the new behavior isn't acceptable, I will need a more complete description of
the behavior you want the IDE to implement
Comment 2 Marco Walther 2006-10-02 22:36:42 UTC
All this happens with the default username/password combination. Nobody has 
tried to change that.

The problem is that sometimes the plugin decides is can't talk to the server 
and brings up the user/passwd dialog. I've also seen that the deployment 
simply fails with a message like wrong username/password. But the next 
deployment is most often fine without changes.

Comment 3 Vince Kraemer 2006-10-02 23:01:07 UTC
this looks like another dup of issue 84932.

reopen with steps to reproduce once VWP is running in an NB 5.5 20061003 (or
newer) environment



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