http - My application on Glassfish 3.1 won't perform client authentication -


i have application consuming soap service uses transport-level authentication. trying move application tomcat glassfish 3.1. unfortunately, glassfish seems reticent perform client authentication needed soap service. ssl stacktrace results in message "uknown_ca".

i have glassfish server configured use keystore contains each of 3 entrust certificates in auth chain (stored -trustcacerts) having imported soap destination server's certificate too.

i have tried several from-scratch rebuilds of glassfish server , resorted trying tomcat server's keystore file no luck.

does know going on, or else how glassfish provide me more useful information regarding handshake , keystores involved (beyond -djava.net.ssl.debug flag).

a co-worker of mine came solution. points andrew.

the destination turned out sending unknown_ca message, did not understand ca of key glassfish sending during authentication process.

removing jvm argument -dcom.sun.enterprise.security.httpsoutboundkeyalias=s1as resolves issue. 1 may change argument specify alias of preferred key instead of letting jvm determine key use.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -