Hi, On Mon, Feb 12, 2018 at 2:25 PM, Naveen Nandyala - Vendor <Naveen.Nandyala@xxxxxxxxxxx> wrote:> > [Mon Feb 12 07:22:12.631833 2018] [ssl:warn] [pid 21729:tid > 139998669920000] AH02268: Proxy client certificate callback: > (Virtual:443) downstream server wanted client certificate but none > are configured This is a different problem, here the Websphere Server is asking for a client certificate (the proxy's) signed by one of its configured CAs for client authentication (i.e. in SSLCACertificateFile/Path or SSLCADNRequestFile/Path). Since no client certificate corresponds on the proxy side (i.e. in SSLProxyMachineCertificateFile/Path), this log is issued. As Eric said, you should take each issue one by one, above is about the Websphere authenticating the proxy, you should first try to make the proxy authenticate the Websphere (see below). > > Was wondering if Apache(Client) don't connect to Websphere (Server) > if Websphere uses a Self-signed certificate? The Apache proxy will connect, but you can't ask it to authenticate the WebSphere server in this case, there is no CA to verify the WebSphere certificate against. You previously said "was.crt" was the root certificate (meaning the one which signed the Websphere server certificate), if it's not the case it can't help in the proxy authenticating the server. Regards, Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|