Help The platform Import and SSO
Connect Okta
On this page
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.
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
ACTIVEis imported as active; any other status imports it as inactive. - Okta’s system groups (
BUILT_INtype, 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 exampleprofile.login,profile.email,profile.firstName,profile.lastName,profile.mobilePhone,profile.primaryPhone,profile.title,profile.department,profile.preferredLanguage, as well asstatus. - 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.
Declare all the redirect URLs shown in SSO sign-in (portal and Academy) as sign-in redirect URIs of the Okta application.
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
| Situation | What to check |
|---|---|
| Connection test fails | Is 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 search | System groups (BUILT_IN) are excluded. The search shows at most 50 groups: refine the text. |
| Organization with encryption active | The test and the synchronization go through the Bexxo Protected agent: it must be started and able to reach your Okta organization. |
Didn’t find the answer? Contact us