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.
I am using 10/11 5.0 IDE daily build. Steps to recreate: (1) Add a server and give valid Admin user and password (2) start server started ok (3) stop server stoped ok (4) Click on Properties, update with invalid Admin user and password (5) start server still started ok, but I am expecting to get a password window pop up for user to input the Admin user and password when detected the invalid Admin user and password. This is the case when I add a server, if I give the invalid Admin user and passwork, I verified that I did get this password window poped up.
Appserver start does not use the username and password as there are not required values for Appserver PE start command. Username and password are required to connect to the server, hence you get the invalid notification on Add Server action. That being said, this might be confusing. But it is not P2 issue, Lowering priority to P3
I think you get the password dialog as soon as you try to access the server (i.e in runtime tab nodes, or when you deploy, undeploy etc)... I just tried with build 11/14 the described scenario and a popup for the password was shown. So cannot reproduce for 9 PE. Reopen with precise click steps if you can reproduce. Mention the server type also ((pe, ee, 8.,1 or 9.0) and the OS you are using.
I am using 10/11 IDE dialy build with JDK 5.0, Appserver 8 UR2 on Win XP Steps to recreate: (1) In IDE,Add a server and give valid Admin user and password (2) In IDE,start server started ok (3) In IDE,stop server stoped ok (4) In IDE, on the server node, click on Properties, update with invalid Admin user and password (5) In IDE, start server, it pop the window this time for the Admin user and password, but at the time when I open this bug, it did not pop up the window, so the behavior of poping up the window may not be consistent. (6) Give valid Admin user and password (7) The start server started ok (8) In IDE, on the server node, click on Properties, I saw the Admin user got updated, but the password field is empty, this is an issue ? (9) In IDE, start server started ok with an invalid password, it did not pop the user and password this time, this back to the issue I opened this bug for (10) In IDE, I can deploy an simple web app and run it, which means some how it knows how to connect to server, not sure where it got the password from, but the password in the properties is empty which is an invalid password.
Sorry to give the above steps twice by mistake.
I did some more testing, and found out in step (10) I could not run a simple application, it failed in the deploy step with the following information in the server.log. This should be the correct behavior since the Admin password is invalid. At this time the deploying task bar keep running, it never got closed. Login failed: javax.security.auth.login.LoginException: Failed file login for admin.
retest with a build done after 10/14 Ludo
I retest with 10/13 build which is the latest build available on 10/17. On this build I got the same behavior in step (10), so the password did not get saved in the properties, howevery the app can run ok and it knows how to connect to the server. So this is P3 and can be looked later on. (10) In IDE, I can deploy an simple web app and run it, which means some how it knows how to connect to server, not sure where it got the password from, but the password in the properties is empty which is an invalid password.
Fixed, mainly File [changed]: AdminAuthenticator.java Url: http://serverplugins.netbeans.org/source/browse/serverplugins/sun/appsrv/src/org/netbeans/modules/j2ee/sun/ide/editors/AdminAuthenticator.java?r1=1.3&r2=1.4 Delta lines: +26 -24 If the password is set to empty, the popup dialog asking for the correct password will used the entered password, but the password will not be saved by the ide at that time for security reason. The password is saved only if the previous password known by the IDE is not empty. This is the answer for point (8)