SSL-Enabled Servers Behaving Differently in iChain 2.0
Novell Cool Solutions: Question & Answer
Reader Rating 
Q:
We've just done an upgrade from iChain 1.5 -> iChain 2.0 + FP3.We had a web server that was being front-ended by the iChain 1.5 box, and itwas already running with SSL on it before iChain was put in, therefore weleft it with SSL enabled. In the configuration on the accelerator in 1.5,we just told iChain to listen on port 443 and that the origin webserver wasalso on port 443. This seemed to work just fine.
After the upgrade to 2.0, all the other webservers were working just fine,however the SSL enabled server was not. This was quite strange. After some trials (delete accelerator, then re-add)nothing changed.
I thought as a last resort I would try the option for "Act as a tunnel." Assoon as this was enabled, all was fine again.
Is this the way that SSL needs to be done in iChain 2? It seems to have changed since 1.5.
A:
With iChain 1.5 when you set the listening and filling port on 443 itautomatically acted as a tunnel. But, that was changed in the iChain 2.0.With 2.0 you need to import the trusted root from the webserver into theiChain box using the secure exchange options on the accelerator.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com