The other way around ... SG is your fontend accessed by https:// which relays the session to the WI. --- mvh/yours Anders Hansen-Øvre, Seniorkonsulent Konsulenthuset Contra as http://www.contra.no <http://www.contra.no/> -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Stuart Hall Sent: 10. september 2003 22:14 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: CSG and WI 2.0 OK, but I want to secure my WI login page with HTTPS. Somehow with WI and CSG on the same box the WI forwards the request back through SG? ____________________________ Msg: #45 in digest Subject: [THIN] Re: CSG and WI 2.0 Date: Wed, 10 Sep 2003 21:03:23 +0200 From: =?iso-8859-1?Q?Anders_Hansen-=D8vre?= <Anders.Hansen-Ovre@xxxxxxxxx> When you install CSG and WI on the same server you don't have to enable HTTPS on your IIS. Just install a server certificate and select the certificate from the SG config. When you access your WI, SG will "relay" your request from the https://wi.company.com <https://wi.company.com> to the WI you selected in your SG config. This way you only have to enable https (port 443) from your unsecure network to the WI/SG server. Hope this helps. --- mvh/yours Anders Hansen-Øvre, Seniorkonsulent