I also want to add some information that could be useful to who buy the SSL certificate in GoDaddy. Later continue with step 11 - restart the server Keytool -import -v -trustcacerts -alias s1as -keystore cacerts.jks -file server.cer Import the alias s1as to cacerts.jks using the server.cer.Keytool -delete -alias s1as -keystore cacerts.jks Keytool -export -alias s1as -file server.cer -keystore keystore.jks
Export the alias s1as from keystore.jks.I only want to add some extra steps that I had to do, these are:
#Glassfish 4 ssl certificate install#
Thank you so much guys and your posts really helped me to install an SSL certificate in Glassfish 4.1. Hope all that background helps, but the TL DR is as follows:
This is because the admin console communicates with the DAS over REST and needs to identify itself as a trusted client. The root cause is that the admin console is essentially doing 2-way SSL along with your login, so your username and password is verified for you, the admin user, then the admin console itself is verified with the DN as a user ID and the s1as key as a password. You will then need to restart GlassFish for the change to take effect, but you will then be able to log in to the admin console. This command will call the same code as the previous one and replace the secure admin principals with the correct ones from whatever the admin certificate alias is (s1as).
#Glassfish 4 ssl certificate update#
There is an asadmin command ( enable-secure-admin-principal) which allows you to manually update this, but you can also just run enable-secure-admin again (even though secure admin is already enabled). The problem is almost certainly that the distinguished name ( DN) of the s1as certificate has changed, but the secure admin principal has not been updated.
0 kommentar(er)
