Good question. I believe the answer is yes with some caveates. The
author and public instance can talk to the client with SSL no problem.
I haven't looked at the activation code in a while, but believe author
and public can't talk to each other over SSL. There will have to be an
unencrypted connector in tomcat on author and public for that.
Tunneling might be an answer if you need that encrypted as well.
I've done the setup with author and public on the same machine. One
connector is SSL enabled for the clients and the other is a standard
HTTP connector with the attribute address="127.0.0.1". That forces the
connector to bind to the localhost interface where the public can't
access it. Setup activation on author and public to use the unencrypted
127.0.0.1 address.
--David
(FTP) wrote:
Hi,
I was looking in the archives as well but couldn't really find aworking
solution how to install/operate Magnolia 2.1.3 when SSL is switched on in the
latest Tomcat version.
Is any info on this?
Thank you
George
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
