Single Sign-On (SSO) Setup

Updated on Aug 31, 2026

The Fiddler Everywhere Enterprise license tier supports single sign-on (SSO), allowing your organization's users to log in to Fiddler Everywhere with their existing identity provider (IdP) credentials instead of a separate Fiddler/Telerik username and password. SSO streamlines authentication and improves security by centralizing access control at the organization level.

The Fiddler Everywhere Enterprise subscription plan is required to enable SSO. For a comparison of the available license tiers, refer to the Commercial Licenses section of the Introduction article.

SSO is configured and managed centrally through your Telerik account and applies to all Telerik and Kendo UI products covered by an eligible DevCraft Complete or DevCraft Ultimate subscription license, including Fiddler Everywhere.

Available SSO Setup Options

Two options are available for enabling SSO:

Self-guided SAML setup (recommended)—Configure SSO directly from your Telerik account dashboard using SAML. This option currently supports the following identity providers:
- Microsoft Entra ID (formerly Azure AD)
- AD FS
- Okta
Assisted setup for other providers—If your organization uses a non-SAML identity provider, the Telerik support team can help you configure SSO through a guided setup process.

Prerequisites

An eligible Fiddler Everywhere Enterprise license as part of a DevCraft Complete or DevCraft Ultimate subscription.
License Holder or License Manager permissions for the license in Your Telerik Account.
Ownership (or IT team access) of the organization's domain to add DNS records for domain verification.
Administrative access to the identity provider (Microsoft Entra ID, AD FS, Okta, or other) to register the SAML application.

Setting Up SAML SSO (Self-Guided)

Step 1: Configure SSO

Log in to Your Telerik Account.
If your license is eligible and you are a License Holder or License Manager, you will see a banner to Configure SSO. Alternatively, navigate to Manage SSO from your account settings.

Step 2: Verify Your Domain

To confirm domain ownership:

Ask your IT team to add the provided challenge key to your domain's DNS records.
Wait until the key is visible via a DNS lookup.
Click Verify Domain.

Domain verification progress is saved automatically, so you can leave and return later to complete the process.

Step 3: Configure Your Identity Provider

Once the domain is verified:

Register the SAML configuration with your identity provider.
Enter the Metadata URL.
Map the required claims: email address, first name, and last name.
Verify that all URLs are mapped correctly.

Incorrect claim mappings result in login failures. When using Okta, make sure to use Name attributes when setting identifiers and claims.

Step 4: Test and Confirm

Test the login URL to verify that the configuration works. Once successful, you will receive a confirmation message that SSO is active.

Do not skip this step. Only proceed to enabling SSO for a specific license after you see the SSO Successfully Configured confirmation message.

Step 5: Enable SSO

Review and confirm that the correct domain is selected for provisioning.
Click Enable SSO to start the setup for the selected license.
Click Apply Changes to complete the process and enable SSO access for all applicable users associated with the license.

To enable SSO for additional licenses later, return to the Manage SSO section in Your Account and repeat this step for any new or existing licenses.

What Happens After SSO Is Enabled

Only users assigned to the enabled license(s) with email addresses matching the verified domain will log in via SSO exclusively. Even if these users previously logged in to Fiddler Everywhere with a username and password, SSO becomes the only supported authentication method going forward.
Affected users receive an email notification with login instructions.
If a license expires, users can still sign in via SSO for 10 days. After that period, they need to recover their password and sign in with a username and password.

You can also automate user access and license assignments through SCIM provisioning. For more information, refer to the SCIM Provisioning blog post.

Considerations

SSO configuration is managed at the Telerik account level, not from within the Fiddler Everywhere application itself.
If your organization also uses the Telerik NuGet server or Visual Studio Extensions (VSX), verify that all affected developers use Telerik NuGet Keys instead of password-based authentication before enabling SSO, since password-based login to the NuGet feed stops working once SSO is enforced.
For non-SAML identity providers, contact Telerik support to request assisted SSO setup.