We’re automating E2E flows for an internal app protected by Okta. On first navigation to our tenant, Chrome shows a “Select a certificate” dialog for *.mtls.okta.com (mTLS client auth). This blocks our Katalon tests because the dialog is outside the page DOM.
Environment
-
Katalon Studio on macOS
-
Chrome/Edge (Chromium)
-
Okta sign-in → mTLS to ….. (company domain)
-
Certificate is issued by our corporate CA and lives in the local device keychain
What happens
-
When navigating to the app’s SSO URL, the browser displays the native client-cert picker (“Subject / Issuer / Serial”).
-
Because it’s a native sheet/dialog, Selenium/Katalon can’t click OK or choose a cert via normal WebUI keywords.
What we’ve confirmed-
The certificate in the dialog is fetched from the local device (keychain), not provisioned through the web page.
-
This is expected behavior for mutual TLS (mTLS) endpoints.
-
WebDriver’s “accept insecure certs” does not apply here (that flag is for server TLS trust, not client-cert selection).
Kindly suggest/recommend any tips on
how to handle and bypass such MFA case, as it is needed to perform as 1:1 testing procedure in the company. There are 2 ways i tried ,
-
one is with a personal account which binded with certificate from local device
-
-
and the second one with dedicated test account which has no ceritificate linked but it is however showing the native pop up from okta that i need to resolve within the automation running. (note: this element is not captured with the tool and popped up from the device)

