For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginTalk to us
DocumentationSDKsConnectAPI Reference
DocumentationSDKsConnectAPI Reference
    • Home
    • Release Notes
  • Getting Started
    • Quickstart
      • How to create a campaign with CSV
      • How to trigger workflow using webhook
      • How to receive delivery reports
      • How to configure Okta SAML Single Sign-On
      • How to configure Arcon SAML Single Sign-On
      • How to Configure AWS - SAML Single Sign-On to Access Fyno
    • Dashboard
    • Alarms
    • Versioning
  • Core Features
    • Integrations
    • Templates
    • Routes
    • Notification Events
    • Requests/Go Live
    • Logs
  • Advanced Features
    • Workflows
    • Campaigns
    • User Profiles
    • Approval Request
  • Settings
    • Profile Settings
    • Workspaces
    • Workspace Settings
LogoLogo
LoginTalk to us
On this page
  • Overview
  • Prerequisites
  • 1. Create a SAML App Integration in Okta
  • 2. Configure SAML Settings
  • SAML Configuration Table
  • Assigning Users
  • 3. Configure Trust Between Okta and Fyno
  • 4. Verify the Integration
  • How This Helps Organizations
Getting StartedTutorials

How to Configure Okta SAML Single Sign-On to Access Fyno

Was this page helpful?
Previous

How to Configure Arcon SAML Single Sign-On to Access Fyno

Next
Built with

Overview

With this example, you will learn how to configure SAML-based Single Sign-On (SSO) between Okta and Fyno. This walkthrough explains the end-to-end setup, what each step accomplishes, and how centralized access management improves security and reduces operational overhead.

With SAML SSO, users can sign in to Fyno using their company login instead of managing separate credentials. Okta acts as the Identity Provider (IdP), and Fyno acts as the Service Provider (SP).

Prerequisites

Before starting, ensure the following:

  • Admin access to the Okta Admin Console.
  • Access to Fyno dashboard with permission to configure SAML.
  • Your Fyno tenant ID (provided by Fyno).

1. Create a SAML App Integration in Okta

In this step, you will create an application in Okta that represents Fyno, allowing Okta to authenticate users and send a trusted SAML response.

  1. In the Okta Admin Console, navigate to Applications.
  2. Click Create App Integration.
  3. Select SAML 2.0 as the sign-in method.
  4. Click Next.
  5. Enter a name for the integration (e.g., YourOrg - Fyno).
  6. Click Next.

2. Configure SAML Settings

This section defines how Okta and Fyno communicate during authentication.

SAML Configuration Table

SettingDescriptionNotes
Single Sign-On URL (ACS URL)Endpoint where Okta sends SAML responses after authenticationExample format: https://..{tenant_id} — contact support@fyno.io for your tenant URL.
Audience URI (SP Entity ID)Identifies Fyno as the Service ProviderStatic value — copy from Fyno SAML settings.
Name ID FormatDefines how the user identity is passedUse Unspecified unless instructed otherwise.
Default RelayState (Optional)Controls post-login redirectLeave empty — defaults to dashboard.

Assigning Users

ActionPurpose
Assign users or groups to the SAML applicationControls who can access Fyno using SSO.

Only assigned users will be able to authenticate.

3. Configure Trust Between Okta and Fyno

To establish secure communication:

  1. Download the SAML signing certificate from Okta.
  2. Upload this certificate in Fyno SAML configuration.
  3. Fyno will then verify SAML assertions are signed and trusted.

4. Verify the Integration

  1. Log out of Fyno.
  2. Initiate login via Okta.
  3. After successful authentication, you should be redirected to the Fyno dashboard.

If access is revoked in Okta, users will automatically lose access to Fyno.

How This Helps Organizations

By using SAML SSO:

  • No separate username/password management.
  • Centralized access control via Okta.
  • Automated onboarding/offboarding.
  • Immediate access revocation when removed in Okta.
  • Reduced security risk and easier auditing.

This streamlines identity management and improves operational security across the organization.