an't begin to tell you how you'd configure that.
To test for certain, sniff the connection.
btw, your question is better suited for the BEA/WLS newsgroups and
forums, or even Apache forums; this mailing list is for OpenSSL itself.
-QM
--
software -- http://www.brandxdev.net
tec
Recon's advantage over using "openssl x509 -text" is that it queries the
server itself, emulating a client. This way, you don't have to worry
about keeping cert files around, file mismatches, etc.
-QM
--
software -- http://www.brandxdev.net
tech news -- http:/
ting as a CA,
the client never sends that to you anyway.
If I've misunderstood your question, please explain/elaborate.
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
___
ral other potential app-design failures, but that's the root
of the matter.
btw, most webservers are highly configurable: there's no guarantee that
a request URI ending in ".php" is indeed PHP, no more than a URI ending
in ".html" is a static file on the server.
-QM
g output and/or run
strace to see where it's hanging. As root, run:
slapd -u ldap -d 255
-QM
--
www.brandxdev.net
C++ / Java / SSL
__
OpenSSL Project http://www.openssl.org
User
erver running on that host, using a different
cert, you'll get the webserver's cert (because your browser defaults to
port 443, for https) and not your ldap cert.
Otherwise, it's back to "slapd -d 255" -- note the file that it's
loading for a cert and run that t
with JSSE it's pretty straightforward as long as you
have other Java networking experience: wrap your plain Socket objects in
SSLSocket objects and go.
-QM
[1] = I have Java code that communicates with all kinds of SSL-enabled
services and I've yet to encounter any toolkit compatibili
