Forgot SSL Database password in Sun Web server 6.1?
By Wing-Yip Walter Lee on Jul 08, 2008
One common question is what to do when you forgot the SSL security database password in Sun Web server 6.1SPx (or your predecessor did not tell you this before he/she left the company, etc.). This is the password you will be asked everytime when you want to start up the SSL enabled web server instance in 6.1SPx,
Sun ONE Web Server 6.1SP9 B01/11/2008 14:24
Please enter password for "internal" token: <-- this is the security database password
Sorry, there is not much you can do in this case. You will need to re-initialize the security database with a new password, e.g. see
then you will need to request a new SSL certificate from the CA and so on,
A couple options you can do to prevent above situations in the future:
1. use a password.conf, e.g.
then you can see your own password such as
"internal:your_password" in password.conf file in the config subdirectory of the server instance.
2. use web server 7.0 which does not ask this internal token password when you request the SSL cert (generate a CSR) , and other later steps (e.g. install the SSL cert, start up the SSL server).
(Important : Jyri has helped to point out in the comments to this posting that
option #2 is only so because WS 7.0 allows you to have an empty password for the cert
database if that's what you want. It's not that it can somehow bypass the password if
one is set. If you do set the password on WS 7.0 (which may or may not be important to
do, depending on the deployment scenario) and later forget it, you'll still have to start
all over again with new keys; certificates.
e.g. No password asked when I requested the SSL cert.
After I installed the SSL cert.,
no password asked when I start up the SSL web server instance,
Sun Java System Web Server 7.0U3 B06/16/2008 12:00
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.]
info: HTTP3072: http-listener-1: https://apple.asia.sun.com:7032 ready to accept requests
info: CORE3274: successful server startup
So, this is another good reason to upgrade to web 7.0