System -> Absolute support for SSL/Non-SSL pages

[craigbrass]

It is under Will Implement for V3 but no date has been set for it.

[Jamie Edwards]

Originally Posted by averkiev

Have you finished testing yet? When the instructions are going to be available?

It's really stupid that this feature is not supported out of the box

Hi averkiev; we have just about finished testing and should be providing instructions / the appropriate changes to the code base in the next minor release (3.20.03).

Regards,

[Jamie Edwards]

Please see the tracker entry for this: Kayako Bug Tracker - Viewing Issue #357 - Full SSL support inc. for chat icon/loader

[Jamie Edwards]

Originally Posted by pkreil

If someone encounters any problems with https-Support, just add the following code to .htaccess (mod_rewrite is needed) and everything will be fine without any modification to the code:

 RewriteEngine On

RewriteCond %{SERVER_PORT} !^443$
# RewriteCond %{REQUEST_FILENAME} !/cron/index.php
RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]

Second Condition is only needed if Cron is triggered external and fails if redicrectet to https.

[averkiev]

Unfortunately this .htaccess trick won't help customers using Kayako in shared Windows-based hosting environments.

[mrloofer]

Why can't SSL be implemented for hosted version of this? helpserve.com can be certificated and implemented within hours. I don't get it ?

[craigbrass]

Why can't SSL be implemented for hosted version of this? helpserve.com can be certificated and implemented within hours. I don't get it ?

Although I am not a hosted customer, I also wondered this. Kayako could either setup a shared SSL and / or allow customers to purchase SSL certs and support install them for the user (which they can do easily with the server using Plesk on it).

[Jamie Edwards]

I'll look into the possibilities of it.

[pkreil]

Originally Posted by averkiev

Unfortunately this .htaccess trick won't help customers using Kayako in shared Windows-based hosting environments.

You need Apache as Webserver to use mod_rewrite, that's correct.
On IIS, you can add Components like ISAPI_Rewrite <http://www.isapirewrite.com> (other will work as well) to add URL-Rewriting capabilities.

I can't provide further help on this because we don't use IIS

[jnet]

I need to solve this too

[mylove4life]

it works , but have to modify the popup as well...

Originally Posted by B00MER

Scenerio, kayako installed under subdir /support/ off public_html

Edit modules/livesupport/visitor_htmlcode.php

Locate:

PHP Code:

ob_start(); 


BEFORE this line add:

PHP Code:

$_SWIFT["swiftpath"] = "/support/"; 


Next locate:

PHP Code:

$proactivetmpl = $template->displayTemplate("proactivechatdiv"); 


Change this line to:

PHP Code:

$proactivetmpl = eregi_replace('http://www.yourdomain.com/support/',"/support/",$template->displayTemplate("proactivechatdiv")); 


Next locate:

PHP Code:

document.write("<?php echo addslashes(str_replace("\n", "", str_replace("\r\n", "\n",$template->displayTemplate("chatimage")))); ?>");

Change this line to:

PHP Code:

document.write("<?php echo addslashes(str_replace("\n", "", str_replace("\r\n", "\n",eregi_replace('http://www.yourdomain.com/support/',"/support/",$template->displayTemplate("chatimage"))))); ?>");

Also be sure you are using https within the JS include statement that you've pasted anywhere:

<!-- Begin SupportSuite Javascript Code -->
<script language="javascript" src="https://www.yourdomain.com/support/visitor/index.php?_m=livesupport&_a=htmlcode"></script>
<!-- End SupportSuite Javascript Code -->

This should cause the JS to load over HTTPS, and any subsequent image requests from within visitor_htmlcode.php that the above script src includes to be rewritten to just /support/ instead of 404 - Not Found making the Mixed HTTP/HTTPS errors disappear.

NOTE, obviously your going to want to change yourdomain.com and support to your relative kayako installation domain and directory.

Hope this helps anyone out, until Kayako can come up with a better out of box resolution.

[jphaynes1966]

We are trying to run our entire site under SSL and are getting those annoying pop-ups in Windows Internet Explorer 7 stating that there are insecure items on the page. We temporarily fixed this by editing the file staffcpmenuclick.js (this is in the cache directory) and replacing the calls to URL's that pull images using HTTP to HTTPS.

Does anyone know how this file is generated and/or if there is a way to fix the program that generates this cache file?

Thank you.

J. Haynes
MindWorks Incorporated.

[jeffshead]

B00mer's fix does not work for me (Kayako v.3).

When I access the client area via https and login as a client, I get the following alert from FF 2.0.0.14 when clicking on the Login button:




I then removed all of the changes and tried the .htaccess fix. This does not work for me either.

If I access http://www.mysite.com/support/, I do get redirected to https://www.mysite.com/support/ but, the login fails and I still get the same FF alert.

UPDATE: I think I fixed it so only the .htaccess fix is needed!!!

I forgot to...
Make sure the URL entered in your software Admin CP > Settings > General matches the URL using which you are accessing the helpdesk with.

From this thread: HTTPS problems

UPDATE #2: Get warning about displaying nonsecure items when accessing Admin control panel.

The icons do not display in the dashboard. When I right click them and view the properties, the images' URL starts with http.

Anyone have any ideas on how to fix the issue with the icons?

[jeffshead]

Originally Posted by jphaynes1966

We are trying to run our entire site under SSL and are getting those annoying pop-ups in Windows Internet Explorer 7 stating that there are insecure items on the page. We temporarily fixed this by editing the file staffcpmenuclick.js (this is in the cache directory) and replacing the calls to URL's that pull images using HTTP to HTTPS.

Does anyone know how this file is generated and/or if there is a way to fix the program that generates this cache file?

Thank you.

J. Haynes
MindWorks Incorporated.

My issue (UPDATE #2) from my previous post, is caused by 'cpadminnavbar.js' which is also located in the 'cache' directory. All of the URL's start with http. All of the URL's in my 'staffcpmenuclick.js' file start with https.

Anyone have any ideas?

[jeffshead]

Originally Posted by jeffshead

My issue (UPDATE #2) from my previous post, is caused by 'cpadminnavbar.js' which is also located in the 'cache' directory. All of the URL's start with http. All of the URL's in my 'staffcpmenuclick.js' file start with https.

Anyone have any ideas?

I just deleted all of the files in the 'cache' directory and so far, all is working great with https!