Skip to content
Bexxo Help

Help The platform Import and SSO

Connect Okta

For administrators Updated on 13 November 2026

Connect Okta to synchronize the organization’s people and groups, and prepare sign-in with the Okta account (SSO).
On this page
  1. Overview
  2. Prepare an API token in Okta
  3. Fill in the Connection section
  4. What is imported
  5. SSO sign-in with Okta
  6. Test and troubleshoot

Overview

Okta is read in read-only mode: users, groups and members. This article covers the preparation on the Okta side and the Connection and SSO sign-in sections; the other settings are shared by all imports.

The settings shared by all importsImport people and set up SSO

1Prepare an API token in Okta

Create an API token (SSWS type) in the Okta admin console, with an administrator account that can read users and groups.

Okta shows the token only once: paste it directly into the portal. If it expires or is revoked, the synchronization fails: create a new one and enter it again.

2Fill in the Connection section

Enter the token and the URL of your Okta organization, in https:// and without a path, for example https://exemple.okta.com. An address in http:// is rejected.

What is imported

  • Only a user with the Okta status ACTIVE is imported as active; any other status imports it as inactive.
  • Okta’s system groups (BUILT_IN type, such as “Everyone”) are excluded and cannot be selected in Imported groups.
  • Properties usable in field matching and filters: each Okta profile attribute in the form profile. followed by its name, for example profile.login, profile.email, profile.firstName, profile.lastName, profile.mobilePhone, profile.primaryPhone, profile.title, profile.department, profile.preferredLanguage, as well as status.
  • For a group: profile.name, profile.description.

Example of a filter by department: Property profile.department, Equals, Vente.

SSO sign-in with Okta

SSO uses an OpenID Connect application of the web application type created in Okta, separate from the API token.

  1. Declare all the redirect URLs shown in SSO sign-in (portal and Academy) as sign-in redirect URIs of the Okta application.

  2. Enter the issuer of your Okta authorization server, for example https://exemple.okta.com/oauth2/default, the client ID and client secret of the application, save, then test discovery.

Enabling SSO and the effects of an outage are described in the general article.

Test and troubleshoot

SituationWhat to check
Connection test failsIs the URL in https:// and does it point to your organization? Is the token still valid, and created by an administrator who can read users and groups?
A group does not appear in the searchSystem groups (BUILT_IN) are excluded. The search shows at most 50 groups: refine the text.
Organization with encryption activeThe test and the synchronization go through the Bexxo Protected agent: it must be started and able to reach your Okta organization.
Organization with encryption activeInstall the Bexxo Protected agent

Didn’t find the answer? Contact us