Sync Okta Users to Jericho Security via SCIM 2.0
Jericho Security supports SCIM 2.0 directory sync with Okta. Once configured, Okta automatically pushes your users and groups into Jericho Security, ensuring your phishing simulation and training campaign targets stay current without manual imports. This guide uses a custom SAML app with SCIM provisioning enabled. Provisioning availability depends on your Okta organization.
Before you begin
Section titled “Before you begin”You will need the following values from Jericho Security during setup:
| Field | Value |
|---|---|
| SCIM connector base URL | https://app.jerichosecurity.com/scim_v2 |
| Authorization Bearer Token | Your SCIM API token from Jericho Security integration settings |
Setup steps
Section titled “Setup steps”Log into Okta as an administrator
Section titled “Log into Okta as an administrator”Sign in to your Okta instance with an account that has administrator privileges.
Create a new app integration
Section titled “Create a new app integration”From the left menu, select Applications, then click Create App Integration.
Select SAML 2.0 as the integration type
Section titled “Select SAML 2.0 as the integration type”Select the SAML 2.0 radio button, then click Next.
Name the application
Section titled “Name the application”Enter an app name, for example Jericho Security Directory Sync.
Hide the app icon and proceed
Section titled “Hide the app icon and proceed”Under App Visibility, check both boxes to hide the application icon from users, then click Next.
Configure the SAML settings
Section titled “Configure the SAML settings”Fill in the following fields:
- Single sign-on URL:
https://jerichosecurity.com - Audience URI:
https://jerichosecurity.com - Name ID format:
EmailAddress - Application username:
Email
These SAML URLs are placeholders for this hidden, provisioning-only app. They do not enable Jericho SSO. For a combined SSO/provisioning app, use the real values in the Okta SSO guide instead.
Click Next.
Complete the app creation
Section titled “Complete the app creation”On the Feedback page, optionally select I’m an Okta customer adding an internal app, then click Finish.
Enable SCIM provisioning
Section titled “Enable SCIM provisioning”In the app, click the General tab, then click Edit. Under App Settings, set Provisioning to SCIM and click Save. Some Okta experiences show Enable SCIM provisioning instead.
Configure the SCIM connection
Section titled “Configure the SCIM connection”Click Provisioning > Settings > Integration, then Edit. Fill in the following:
- SCIM connector base URL:
https://app.jerichosecurity.com/scim_v2 - Unique identifier field for users:
userName(map the application username to the employee’s email address) - Supported provisioning actions: check Push New Users, Push Profile Updates, and Push Groups
- Authentication Mode:
HTTP Header - Authorization Bearer Token: your SCIM API token from Jericho Security integration settings
Test the connector configuration
Section titled “Test the connector configuration”Click Test Connector Configuration. Confirm the test succeeds for the provisioning actions you enabled. Import actions are not required for this outbound provisioning setup.
Save the SCIM connection
Section titled “Save the SCIM connection”Click Save to apply the SCIM connection settings.
Enable user provisioning actions
Section titled “Enable user provisioning actions”Still in the Provisioning tab, open Settings > To App and click Edit. Enable all three options:
- Create Users
- Update User Attributes
- Deactivate Users
Click Save.
Assign users and groups
Section titled “Assign users and groups”Go to the Assignments tab, click Assign, and assign the app to all the people and groups you want to target with Jericho Security phishing simulations and training emails.
Push group objects and memberships
Section titled “Push group objects and memberships”App assignment provisions users; it does not by itself create groups in Jericho. Use the Push Groups tab to select the groups whose membership should sync. Use separate groups for app assignment and Group Push, as required by Okta.
Verify provisioning
Section titled “Verify provisioning”Assign a test user and push a test group. Confirm the employee email and group membership appear in Jericho People & Groups before expanding the scope. Review errors in Okta if they do not appear. There is no universal Force Sync step for this workflow.
See Okta’s SCIM provisioning guide and app assignments and Group Push.