Does Katalon support 2FA? Use SSO to enforce MFA through your Identity Provider

If someone on your team asked “how do I turn on 2FA in Katalon?” and couldn’t find the option, this guide is for you. Katalon doesn’t have a separate 2FA toggle. Instead, you can use Single Sign-On (SSO), which gives you the same result through your own Identity Provider (IdP).

Is this you?

  • Someone on your team asked how to enable 2FA and didn’t find it in Security Settings.
  • Your company already enforces MFA through an Identity Provider such as Okta, Microsoft Entra ID (Azure AD), Auth0, or Ping, and you want Katalon to follow the same policy.
  • You want people who join or leave the company to get or lose Katalon access automatically, without someone adding or removing them by hand.
  • You need to show auditors or security reviewers that Katalon login follows your company’s identity standard, not a separate password.
  • You’re on a True Enterprise subscription, or open to moving to one. This is the plan that includes SSO.

How it works

Katalon doesn’t run its own 2FA prompt. It hands the login to your Identity Provider using the SAML 2.0 standard. Your IdP checks the second factor before the user ever reaches Katalon.

User logs in (browser)
   → Katalon True Platform redirects to your IdP
   → Your IdP (Okta / Entra ID / Auth0 / Ping) enforces MFA based on your policy
   → IdP sends a SAML assertion back
   → Access granted to True Platform

Katalon never sees the second factor. Your IdP checks it and then tells Katalon the user is verified.

So “Katalon doesn’t have 2FA” doesn’t mean your account is less secure. With SSO, Katalon login follows the same MFA policy you already run for the rest of your company’s tools.

What this solves

“We want 2FA but can’t find the option in Security Settings.”
There isn’t a standalone 2FA setting for standard login, on any plan. It’s not hidden behind a plan, it just isn’t a separate feature. SSO is the way to do it. Once SSO is on, your IdP handles login and applies whatever MFA policy you have there.

“We don’t want a second password just for Katalon.”
With SSO set to Require SSO, users sign in only through your IdP. There is no separate Katalon password to manage, reset, or lose to phishing.

“Adding and removing users by hand when people join or leave is risky.”
Turn on SCIM provisioning together with SSO. SCIM syncs users, roles, and access from your IdP automatically, so when you offboard someone in your IdP, they lose Katalon access too.

“We also want to limit which networks can log in.”
IP Address Restriction is on the same plan as SSO, and you can use both together for extra control.

Who does what

Who What they do Where How often
Account Admin or System Admin Turns on SSO and pastes the IdP metadata into Katalon True Platform Account Settings > System > General > General Setting > Custom Domain and SSO Once
Your IdP admin Sets up the SAML 2.0 app and generates the IdP metadata (XML) Okta, Microsoft Entra ID, Auth0, Ping, or any SAML 2.0 IdP Once
Account Admin (Optional) Turns on SCIM so users are added and removed automatically Same Custom Domain and SSO page Once, after SSO is on
Everyone else Logs in as usual. The IdP screen and its MFA prompt simply appear first Katalon login page Each login

Step by step: turning it on

  1. Check you’re eligible. You need a True Enterprise subscription and the Account Admin or System Admin role.

  2. Prepare your Identity Provider. In Okta, Microsoft Entra ID, Auth0, Ping, or any SAML 2.0 provider, set up Katalon as a SAML application and export the metadata XML.

  3. Open the settings page. In Katalon True Platform, go to Account Settings > System > General > General Setting > Custom Domain and SSO.

  4. Turn on Enable SSO.

  5. Choose how strict it is:

    • Require SSO: every user must sign in through the IdP.
    • Optional SSO: users can choose SSO or standard login.

    Most teams start with Optional, check that it works, and then switch to Required.

  6. Paste the IdP metadata XML into the Metadata field.

  7. Click Save Changes.

  8. (Optional) Turn on SCIM. Toggle Enable SCIM Provisioning to get a SCIM Base URL and Bearer Token. Then set the Attribute Management Authority (IdP-managed or Katalon-managed) for attributes such as License Type, Role, and Department.

  9. Test before you enforce it. Ask one user to sign in with SSO first. When the login works end to end, switch to Require SSO.

Requirements at a glance

  • Plan: True Enterprise subscription. The same plan also includes Custom Domain, SCIM, and IP Address Restriction.
  • Role: Account Admin or System Admin to set it up.
  • Identity Provider: Any SAML 2.0 provider. Okta is the one our team has tested most, and Microsoft Entra ID, Auth0, and Ping also work.

Official docs

Exact screens and requirements can vary by account and Katalon version.


Questions about your setup? Reply below with your Identity Provider and where you got stuck. Please leave out metadata XML, tokens, and any internal URLs.

Useful guide @Bella , thanks. A few follow-ups that may help others reading this:

  1. Before switching to Require SSO, make sure there’s a tested fallback admin path (and check with Katalon how a locked-out account is recovered), so an IdP misconfiguration can’t lock everyone out.
  2. A question for the team: CI/KRE runs use API keys rather than interactive login. Are those unaffected by Require SSO, and what happens to a user’s API keys when SCIM deprovisions them? Worth adding to the offboarding section.
  3. How often users are re-prompted for MFA depends on your IdP’s policy, not Katalon.
  4. A different problem people hit with the same search: automating login to an app under test that has 2FA. As far as I know there’s no built-in keyword for it. Common options are generating the TOTP code in a custom keyword from the shared secret using a Java OTP library, or using a test account with MFA bypassed in non-prod.