1) change ide password in Tomcat's properties panel
2) restart NB and start Tomcat
3) Tomcat Manager Application dialog box is
appeared. I type ide and correct ide password.
4) Restart NB and then start Tomcat. The admin's
password dialog is appeared again
When Tomcat module tries to make an HttpURLConnection to Tomcat
Manager web application, it tries to pass username and password as a
request property during connection opening. If the username or
password is incorrect, Java transparently calls the default
Authenticator (which is org.netbeans.core.NbAuthenticator) to obtain
authentication for this network connection. There is currently however
no way how to obtain supplied u/p from the NbAuthenticator.
Therefore username & password cannot be saved and after restarting NB
and starting Tomcat, authentication dialog is displayed again.
Thank you for your intimate investigation. Please add a link to the
enhancement filled agains core module concerning the possibility to
obtain the entered u/p from the NbAuthenticator.
As wee agreed I propose to modify the tomcat-users.xml file
appropriately when an user changes the username or the password via
tomcat instance properties editor. So the next attempt to connect to
the tomcat's manager will containt right u&p and the annoying dialog
Here is the link to that issue in core: issue 46331.
The final agreement is that changes made in username and password in
the properties editor will not be reflected in tomcat-users.xml file.
The only reason why user should be interested in changing those values
is when he would manually change his tomcat-users.xml file or when he
would been using another method (Realm) for authentication to the
Tomcat Manager application.
What still needs to be changed is when an authentication dialog
appears entered values should be stored.
It should be implemented ASAP - 4.2?
Moving to j2eeserver.
The current suggestion how to solve the Authenticator issue is to create a proxy
Authenticator in the j2eeserver, which would delegate authentication of server
request to plugins and would use a general authenticator for other requests.
removing 4.2-candidate status whiteboard, we can't make it into 4.2
*** Issue 71778 has been marked as a duplicate of this issue. ***
Obsolete milestone, please reevaluate