Demoaut.katalon.com doesn't support a secure connection with HTTPS

My environment

  • macOS 14.7.6
  • Katalon Studio Free 10.2.1

Incident

I created a new katalon project based on the sample project “Healthcare tests”

I did “Update WebDriver” for Chrome.

Updating web driver...

Checking WebDriverManager
Verify built-in web driver manager
Using built-in file
[INFO] Using WebDriverManager to resolve chrome
[DEBUG] Detecting chrome version using online commands.properties
[DEBUG] Running command on the shell: [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome, --version]
[DEBUG] Result: Google Chrome 137.0.7151.104
[INFO] Using chromedriver 137.0.7151.70 (resolved driver for Chrome 137)
[DEBUG] Using URL built from repository pattern: https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.70/mac-x64/chromedriver-mac-x64.zip
[DEBUG] Driver to be downloaded chromedriver 137.0.7151.70
[INFO] Downloading https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.70/mac-x64/chromedriver-mac-x64.zip

I ran the Test Case “TC1_Verify Successful Login”.

Then, I got the following display:

It said “demoaut.katalon.com doesn’t support a secure connection with HTTPS”. I was disturbed by this. But, when I click the button “Continue to site”, the test began running.

using different version

I downgraded Katalon Studio version v10.2.0. It behaved differently.

With v10.2.0, I was not disturbed by the display with “xxx doesn’t support a secure connection with HTTPS”.

Study

I could confirm that

  • Katalon Studio v10.2.1 launched Chrome for Testing
  • Katalon Studio v10.2.0 launched Chrome-branded Chromium (A.K.A, usual Google Chrome browser)

Workaround

I found the following Q&A in Stackoverflow

With v10.2.1, I configured the Project Settings>Desired Capability>WebUI>Chrome as follows:


I added an argument to Chrome:

--unsafely-treat-insecure-origin-as-secure=http://demoaut.katalon.com

Then testcase ran smoothly.

Discussion

The argument --unsafely-treat-insecure-origin-as-secure=http://xxxxxx.xxxx.xxx takes a value, e.g, ‘demoaut.katalon.com’. I feel it is annoying to give that value for each individual cases.

It seems that Chrome for Testing warns about “insecure origins” but Google Chrome-branded Chromium doesn’t. Why? How Google Chrome-branded Chromium lets me work around the warning without any configuration? — I don’t know. Does anyone know it?

Katalon should add a new URL https://demoaut.katalon.com in addition to the http://demoaut.katalon.com, and modify the sample “Healthcare” project. I mean, Katalon should change the server of demoaut.katalon.com so that it is reachable with scheme https:.

4 Likes

Thank you for making this detailed post. I am also encountering the same. Hope the Katalon team will sort this out asap.

1 Like

Hi all,

Thank you for letting us know this. I have created a ticket for our team to investigate it. Back here soon if anything new. Thank you

2 Likes

Hi @kazurayam,

I got the update that it’s working well on 10.2.2 which we have recently released, can you guys please help check and let me know if it works/not work. Thank you

No, I can’t.

The Release note v10.2.2 mentions nothing about the issue of “xxx doesn’t support a secure connection with HTTPS”. I have no idea what katalon did in the v10.2.2.

The issue was resolved, it was due to an expired SSL cert. Nothing to do with 10.2.2

I assume that @philipB renewed the SSL cert for the https://katalon-demo-cura.herokuapp.com/ (the URL http://demoaut.katalon.com is redirected to it).

If @philipB is right, then Katalon Studio v10.2.1 should let me get access to the demoaut.katalon.com today. I examined this, and found this issue is NOT resolved with v10.2.1.

I tried just the same operation as the original post. I used macOS 14.7.6, Katalon Studio Free v10.2.1. I newly created a project based on the sample project “Healthcare tests”. I did “Update WebDriver” for Chrome. I ran the Test Case “TC1_Verify Successful Login”. Then I got the following display:

This proves that the problem is still there in v10.2.1. I am afraid @philipB is confused with some other issues.

I had a look at v10.2.2. It worked fine. I don’t know how Katalon changed their product to work around this issue.