Identity Management

Active Directory Integration (LDAP)

This article is a guide on integrating Active Directory with the Halo system using LDAP. It explains setting up a new LDAP connection, including configuration details for connecting to a domain controller, field and user/agent mappings, and synchronization using Halo integrators. Key components include necessary credentials, mapping associations between LDAP and Halo fields, and details for integrating child domains. The article also provides information on selecting integrators based on password exposure preferences and managing client ID access for on-premise integrations.

ADFS Integration

Authentication Methods for Microsoft Integrations

This article provides a guide on authentication methods for Microsoft integrations, including setting up App Registration, and using secret, certificate, and federated credential authentication. It covers the basic setup of App Registration, details on handling permissions, and outlines steps for each authentication method. It emphasizes understanding the types of permissions and configuring policies when integrating with Microsoft systems. The guide includes troubleshooting steps for unsuccessful authentication attempts.

AuthRocket Integration

Azure Deltas

This article explains Azure Deltas, a feature in Microsoft Entra and CSP integrations, allowing for efficient data handling by updating only modified records through the Microsoft Graph API. Benefits include more frequent and timely user data updates. Enabling Azure Deltas changes how data is processed by ignoring site mappings during retrieval but applying them during processing. The guide details enabling steps, considerations like initial sync duration, manual import recommendations, and adjustments such as delta sync methods, user deactivation options, and its use in Intune integrations.

Delinea (Formerly Centrify) Integration

Google Workspace Integration

This article details the process of integrating Google Workspace with Halo. It covers configuration steps, including obtaining client IDs, setting up project credentials in Google Cloud, and enabling necessary APIs. The integration allows for user and agent imports, site/agent mappings, advanced mappings, and asset imports. License management and subscription data imports are also addressed. Special configurations for Google resellers and automated data syncing via the Halo Integrator are provided. Common errors and solutions are discussed, along with options for enabling Google Sign-In within Halo.

KeyCloak Integration

Microsoft CSP Integration

The Microsoft CSP integration is designed for importing user data from Azure tenants managed under the Microsoft Cloud Reseller Program (CSP). It's mainly used by organizations with multiple client Azure tenants through CSP and facilitates user and device information retrieval. The article details the setup process, including configuring app registrations in Azure, setting API permissions, and managing customer and tenant mappings. It also addresses user and asset import settings, licensing, and subscription management. The integration requires specific configurations in the Halo system and permissions in Azure.

Microsoft Entra ID Integration (Formerly: Azure Active Directory)

The article provides a comprehensive guide on integrating Microsoft Entra ID (formerly Azure Active Directory) with Halo applications. It details the setup process for app registration, single sign-on (SSO) configuration, and agent/user import. It explains how to grant permissions to non-admin agents for setup, utilize multi-tenancy, and select authentication methods. The guide covers advanced configurations, including field and site mappings, role and team mappings, license management, and import synchronization using the Halo Integrator. Additionally, it discusses delta queries and inbound logging for efficient data management.

Microsoft Entra ID: Single Sign-On (B2B)

Microsoft Entra ID: Single Sign-On (B2C)

The article discusses the setup and use of Single Sign-On (SSO) for Business to Customer (B2C) using Microsoft's Azure platform. B2C SSO allows users and agents to sign into the Halo portal using credentials from various accounts like Google or Microsoft. The guide outlines configuration steps, including creating an Azure application and setting up user flows. Microsoft plans to phase out B2C licensing by 2026 for certain tiers, recommending the use of Microsoft's Entra External ID platform instead. Additional settings for enhancing the login experience, such as bypassing 2FA, are also explained.

Okta Integration

This article is a guide on integrating Okta with Halo. It covers the creation of tokens and applications in Okta, setting up Okta Single Sign-On (SSO) in Halo, and configuring mappings and user roles. It also details how to handle errors and set up SSO for multiple Halo instances. The guide emphasizes using the "Super Admin" role in Okta and outlines steps for manual and automatic user imports. Additionally, it provides solutions for potential login issues when using Okta with Halo.

SailPoint Identity Now Integration

SailPoint Integration

SAML 2.0

This article provides a comprehensive guide on configuring SAML 2.0 in Halo for versions after 2.104.1. It covers key terms, the login flow, metadata exchange, IdP configuration, and issue debugging. SAML allows for secure single sign-on where identity providers authenticate user identities. The guide details both SP-initiated and IdP-initiated login flows, metadata file exchanges, and essential configuration settings for both the IdP and SP. It also outlines common errors and solutions for debugging SAML issues, ensuring a secure and efficient authentication process.

SeatGeek Integration

Single Sign-On (SSO) in Halo

The guide explains setting up Single Sign-On (SSO) in Halo, detailing different identity providers like Microsoft Entra, Google, and Okta. It covers configuration steps, customization of SSO buttons, user provisioning, and how to match users with their Halo profiles using claims. The guide also discusses automatic user creation during sign-in, configuring behavior settings, and restricting access based on claims, ensuring streamlined user access management across linked instances.