Authentication

Migrated from Split?

This documentation describes the Split legacy Authentication experience.

If your organization is using Harness FME, authentication practices and the UI may differ. For more information, see SSO for Split Admins and Account Migrated to Harness.

Overview

Use the following topics to set up and manage authentication for your organization in Harness FME.

Single sign-on (SSO)

• Single sign-on overview
• Single sign-on with Azure
• Single sign-on with AD FS
• Single sign-on with G Suite
• Single sign-on with Okta
• Single sign-on with OneLogin

SCIM

• SCIM overview
• SCIM for Microsoft Entra ID
• SCIM for Okta

Two-factor authentication (2FA)

• Two-factor authentication (2FA)

Session management

The Split console uses a single important cookie: split-token, which stores the user’s JSON Web Token (JWT) credentials after authentication.

This cookie is required to maintain the user’s session while they are logged in.