Web Proxying to a WebLogic Cluster using the HTTPS protocol

Question

Hi all,
I am recently involved into JWS proxying to WebLogic Cluster.
I don't have any technical problems at the moment but "conceptual" problems, that is:
- my jws proxy server should connect to a WebLogic Cluster through a Bea plugin configured wish SSL parameters;
- my jws proxy server should pass the incoming request using a load-balancing algorithm among the two nodes of the cluster, that are actually installed on two different machines;
- the jws proxy server doesn't seem to accept multiple certificates.
My question is: how can I configure my proxy plugin to route the incoming requests to my WebLogic Cluster using the https protocol? As a matter of fact, each certificate should be hostname dependent, and it looks like that the proxy plugin doesn't accept a multiple certificate configuration (and it should actually match the CN entry in the certificates with the actual hostnames of the nodes).
Any hint?
Thx a lot,
Luca

Answer 1

It is supported in 5.2
          - Prasad
          Wei Guan wrote:
          > As I knew of, secure proxying is not supported yet.
          > --
          > Cheers - Wei
          > Bob Kiep <[email protected]> wrote in message
          > news:8bvvc7$7uf$[email protected]..
          > > The NSAPI plugin cannot perform SSL proxying, as documented at the bottom
          > of
          > > this message (taken from
          > > http://www.weblogic.com/docs/admindocs/nsapi.html#background). When
          > > Weblogic is the proxy, can I do SSL? If someone could send me the link to
          > > where is states whether is SSL or not would be very helpful.
          > >
          > > "The plug-in is for an environment where NES serves static pages, and a
          > > Weblogic Server (operating in a different process, possibly on a different
          > > host) is delegated to serve dynamic pages (such as JSPs or pages generated
          > > by HTTP Servlets). The connection between WebLogic Server and the NSAPI
          > > plug-in is clear text http, not SSL. To the end user -- the browser -- the
          > > HTTP requests delegated to WebLogic appear to come from the same source as
          > > the static pages. In other words, WebLogic on the back-end is invisible.
          > > Additionally, the HTTP-tunneling facility of the WebLogic client-server
          > > protocol can operate through the plug-in, providing access to all WebLogic
          > > services (not just dynamic pages). "
          > >
          > >
          Cheers
          - Prasad