Hi there !
So, first things first :
Using port 80 or port whatever doesn't really matter, if you are connecting to an interface configured with Security enabled , then it is going to be https! So, changing to any other port wont change the behavior you are having now , it will only change the URL you are using to access that interface.
Now, about the "Unable to connect" error on the browser:
This is happening because "Client Authentication" is configured for that interface. What happens is this : You connect to the interface, glassfish sends you the certificate and is expecting a certificate in response to that. Because your browser does not contain a valid certificate ( one for example issued from the same CA that issued the server cert, or one issued from a Valid CA ) the browser does not send the certificate, therefore client authentication is not performed, therefore the app server closes socket, and you get a browser error like that.
So, to answer your question : What you did wrong? It depends on your goal. If you just want to have a socket configured to use SSL , then what you did wrong was enabling the "Client Authentication".
If you truly want Client Auth , then go and generate a Client Cert . You can do this at verisign for free and teh certificate will be valid for one month I think, not too sure tho. Install the Certificate on your browser keyring , and try again connecting to that URL.
A brief history recap :
In older versions of the Sun App Server client authentication had three modes : Enabled, Disabled, OPTIONAL . Now, there are only two modes : Enabled , Disabled . In case you are looking for the "Optional" mode for Client Authentication, there is none and this is usually achieved by a proxy in front of the App Serv Farm, you can use the Sun Web Proxy that comes with the Sun WebServer for that.
Hope this helps you with your stuff
Rui
[Message sent by forum member 'syshex' (syshex_at_gmail.com)]
http://forums.java.net/jive/thread.jspa?messageID=364200