HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=27)
-   -   Howto integrate SSL Proxy Feature into ISPConfig 3? (http://www.howtoforge.com/forums/showthread.php?t=36282)

Master One 11th June 2009 12:24

Howto integrate SSL Proxy Feature into ISPConfig 3?
 
I already posted about that matter in 2008 for ISPConfig 2 here.

Has that feature been incorporated in ISPConfig 3?

As I guess not, is the shown solution still valid for ISPConfig 3?

A SSL Proxy is must-have feature, because I want to pay only for one normal SSL certificate, and use that one on https://ssl.masterdomain.tld, so that all other hosted sites can be accessed by https://ssl.masterdomain.tld/hosteddomain.tld/, instead of having to pay for a wildcard cert or multiple individual certs.

till 11th June 2009 18:49

Quote:

Has that feature been incorporated in ISPConfig 3?
No.

Quote:

As I guess not, is the shown solution still valid for ISPConfig 3?
No.

Quote:

A SSL Proxy is must-have feature, because I want to pay only for one normal SSL certificate, and use that one on https://ssl.masterdomain.tld, so that all other hosted sites can be accessed by https://ssl.masterdomain.tld/hosteddomain.tld/, instead of having to pay for a wildcard cert or multiple individual certs.
If its a must have for you, feel free to implement it.

Master One 11th June 2009 19:23

I would, if I could.

till, you yourself found this feature useful, and added it as feature request to the bugtracker in March 2008. It seems to be common setup at ISPs, any ISP I've used so far offered such a shared SSL.

So if the shown solution for ISPConfig 2 does not work any more with ISPConfig 3, any idea how this one could be solved? I am willing to play around with it, once I have my machine up and running, but if it is too complicated to do, I guess I've to pass on that must-have.

till 11th June 2009 19:45

Quote:

till, you yourself found this feature useful, and added it as feature request to the bugtracker in March 2008. It seems to be common setup at ISPs, any ISP I've used so far offered such a shared SSL.
I never needed it as I use dedicated IP's and certificates for SSL sites. I added it to the bugtracker only because a user requested it.

Master One 11th June 2009 20:06

Nevertheless, can you please tell me, why the shown solution for ISPConfig 2 does not work any more with ISPConfig 3?

till 12th June 2009 08:40

ISPConfig 2 and 3 are two completely differnt software packages, so guides or extensions written for ispconfig 2 are not working on ispconfig 3. Rewrite proxy will work somehow on ispconfig 3 too of course but you will have to dig a bit deeper inro the configuration of the vhosts to see how it can be integrated.

Master One 12th June 2009 09:37

Ok, I will look into it, once I have it up and running. I didn't expect that feature to be problem concerning the ISPConfig 2 / 3 differences, because your directions were:
Quote:

Add this configuration in your apache2.conf or httpd.conf file right before the include for the Vhost_ispconfig.conf file.
which means, it should not interfere with the vhosts configuration.


All times are GMT +2. The time now is 22:41.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.