Once in a while a server certificate has to be replaced. Her is a snag in Glassfish 3.0.1 that I have discovered:
After a certificate change (while Glassfish is taken down, of course),
'asadmin --secure start-domain domain1' does not complain about the changed certificate, but then
'asadmin --secure stop-domain domain1' [i]does[/i] complain, and asks the user if it should be trusted.
However, these commands are typically run in a script (like /etc/init.d/glassfish) and [i]not[/i] by a user! This causes hard-to-diagnose failures.
Is there a way to tell asadmin to trust any cert, shut up, and do what it's told without pestering the user (who isn't around anyway)?
[Message sent by forum member 'tmpsa']
http://forums.java.net/jive/thread.jspa?messageID=486337