Okta SAML SSO Integration
Learn how to integrate Fiddler with Okta for seamless Single Sign-On (SSO) authentication using the Security Assertion Markup Language (SAML) protocol.
Overview
This integration allows your users to access Fiddler using their existing Okta credentials. Users are automatically provisioned in Fiddler on their first successful login, eliminating the need for manual user invitations.
Prerequisites
Before starting, ensure you have:
Okta Administrator Access: Permissions to create and configure applications in your Okta organization
Fiddler AuthN Administrator Access: "Org Owner" role in Fiddler's AuthN management console
Deployment Information: Your Fiddler deployment base URL
Configuring Okta and Fiddler for Integration
Add and Configure New SAML Provider
Select the SAML option in the Add provider section which brings up the Sign in with SAML form.
Choose a name for the Okta SAML integration. Note that this name will be displayed on the SSO login button on the Fiddler sign-in page so choose a name your users will recognize.
Paste the following placeholder value into the Metadata Xml text area. This is necessary for AuthN to create the URLs needed when you create the Okta app integration. It will be replaced in a later step.
PD94bWwgdmVyc2lvbj0iMS4wIj8+DQo8bWQ6RW50aXR5RGVzY3JpcHRvciB4bWxuczptZD0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6Mi4wOm1ldGFkYXRhIg0KICAgICAgICAgICAgICAgICAgICAgdmFsaWRVbnRpbD0iMjAyNS0wOC0zMFQxMzo0NToxM1oiDQogICAgICAgICAgICAgICAgICAgICBjYWNoZUR1cmF0aW9uPSJQVDYwNDgwMFMiDQogICAgICAgICAgICAgICAgICAgICBlbnRpdHlJRD0iaHR0cDovL2xvY2FsaG9zdDo4MDgwIj4NCiAgICA8bWQ6U1BTU09EZXNjcmlwdG9yIEF1dGhuUmVxdWVzdHNTaWduZWQ9ImZhbHNlIiBXYW50QXNzZXJ0aW9uc1NpZ25lZD0iZmFsc2UiIHByb3RvY29sU3VwcG9ydEVudW1lcmF0aW9uPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiPg0KICAgICAgICA8bWQ6TmFtZUlERm9ybWF0PnVybjpvYXNpczpuYW1lczp0YzpTQU1MOjEuMTpuYW1laWQtZm9ybWF0OnVuc3BlY2lmaWVkPC9tZDpOYW1lSURGb3JtYXQ+DQogICAgICAgIDxtZDpBc3NlcnRpb25Db25zdW1lclNlcnZpY2UgQmluZGluZz0idXJuOm9hc2lzOm5hbWVzOnRjOlNBTUw6Mi4wOmJpbmRpbmdzOkhUVFAtUE9TVCINCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBMb2NhdGlvbj0iaHR0cDovL2xvY2FsaG9zdDo4MDgwL2NvbnN1bWUvZGF0YSINCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBpbmRleD0iMSIgLz4NCiAgICAgICAgDQogICAgPC9tZDpTUFNTT0Rlc2NyaXB0b3I+DQo8L21kOkVudGl0eURlc2NyaXB0b3I+

Create New App Integration in Okta
Open your Okta Admin console and navigate to the Applications page and select the Create App Integration button:
In the sign-in method modal, select SAML 2.0 and select the Next button:
Name your Fiddler instance per your company guidelines and select the Next button:
Configure the Okta App
Enter the ACS Login Form URL from Step 5 into the Single sign-on URL text box
Ensure the Use this for Recipient URL and Destination URL checkbox is selected
Enter the Metadata URL from Step 5 into the Audience URI (SP Entity ID) text box
Enter the Metadata URL from Step 5 into the Audience URI (SP Entity ID) text box:
Expand the Advanced Settings section
In the Other Requestable SSO URLs section, select the + Add Another button and enter the ACS Intent API URL copied the AuthN console's identity provider page and enter 0 for the Index
In the Attribute Statements section, add the required attributes setting Name format as Basic for all entries:
Name=firstName, Value=user.firstName
Name=lastName, Value=user.lastName
Name=email, Value=user.email
Select the Next button. No changes are required on this page
Select the Finish button to complete the creation of the application
Copy the Metadata URL value on Sign On page from the SAML 2.0 section
Activate the Okta SAML IdP
Select your IdP from the list that the Metadata XML field is populated. The contents were dynamically inserted from the Metadata URL.
At the top of the page, select the Activate button to enable this IdP login.
Select Login Behavior and Security from the left nav menu and ensure the External login allowed checkbox is selected.
Create a Custom Action
Select the Actions tab from the top menu

Select the New button in the Scripts section to create a new action script
Copy the Okta SAML Action Script below and paste it into the script text area
Enter
setAttributesOnOktaSAMLAuth
in the Name text boxSelect the Add button
function setAttributesOnOktaSAMLAuth(ctx, api) {
let firstName = ctx.v1.providerInfo.attributes["firstName"];
let lastName = ctx.v1.providerInfo.attributes["lastName"];
let email = ctx.v1.providerInfo.attributes["email"];
let groups = ctx.v1.providerInfo.attributes["groups"];
let nameParts = [firstName, lastName];
let filteredParts = nameParts.filter(part => part);
let displayName = filteredParts.join(' ');
if (firstName != undefined) {
api.setFirstName(firstName);
}
if (lastName != undefined) {
api.setLastName(lastName);
}
if (email != undefined) {
// Email is returned as an object in SAML response.
// We typecast it to string before normalizing it.
email = String(email).toLowerCase();
api.setEmail(email);
api.setEmailVerified(true);
api.setPreferredUsername(email);
}
if (displayName != undefined) {
api.setDisplayName(displayName);
}
api.v1.user.appendMetadata('fiddler_authentication_type', 'SSO:OKTA:SAML');
if (groups === null || groups === undefined){
groups = []
}
api.v1.user.appendMetadata('fiddler_groups', groups);
}
Validate the Integration
Enter your Fiddler URL. This is https://example1.dev.fiddler.ai in our example. Your Fiddler URL will vary according to your company name and the Fiddler deployment type.
Ensure you see the Fiddler Sign-on page and that the page displays the SSO Login - Okta SAML button:
Select the button and confirm that the Fiddler application loads:
Getting Help
For additional assistance:
Review Okta system logs for authentication attempts
Verify network connectivity between Fiddler and Okta
Contact your Fiddler representative with specific error messages
Reference Documentation
For detailed configuration guidance, refer to the official documentation:
Okta SAML Configuration Guide - Comprehensive setup instructions
General SSO Authentication Guide - Overview of SSO concepts and troubleshooting
Mapping AD Groups to Fiddler Teams - Group synchronization details
Important Notes
Automatic User Provisioning: Users are automatically created on first successful login—no manual invitations required
Data Storage: Fiddler stores only the user's first name, last name, email address, and SAML token from Okta
API Access: For programmatic API access, users must create access tokens from the "Credentials" tab in Fiddler's Settings page
Single Authentication Method: Users can only authenticate via either SSO or email authentication, not both
Next Steps
After successful integration:
Train Users: Provide guidance on accessing Fiddler through Okta SSO
Configure Teams: Set up Fiddler teams to match your organizational structure
Test Group Sync: Verify automatic group synchronization is working as expected
Monitor Usage: Review authentication logs and user access patterns