Have A Question?

< All Topics
Print

Integrate your SCIM endpoint with Other Directories (e.g. Okta)

Integrate Generic SCIM Provisioning Service for NEONNOW (e.g. Okta)

Any SCIM-enabled user directory or Identity Provider (IDP) can be configured to automatically provision phone directories within NEONNOW.

The following are a list of pre-requisites for this integration:

  • NEONNOW Admin Access – to configure the new NEONNOW directory
  • IDP/Directory admin access – to configure an application
  • IDP/Directory user & group setup – a user group should be set up, that your users are members of
  • All users that will be ingested should have a valid E164 phone number configured.  Note – this phone number field should have any spaces removed to ensure the Call History search functions correctly in NEONNOW

This guide uses Okta as an example, however this SCIM principles can be applied to any other SCIM-enabled directory.

Once the pre-requisites are complete, to add a new Directory, select the ‘Add Directory’ icon from within NEONNOW Admin:

NEONNOW Config

Enter a meaningful name & select ‘Other Directory’ then select ‘Next Step’

Take a note of the security token (save it somewhere secure) that is displayed. Also expand ‘SCIM Configuration’ and save the Base URL.  You will need these later in the setup (but you can come back to it). Select the ‘Next Step’ option.

On the next page, select ‘Finish’.

Now, the NEONNOW configure is complete, and it is time to configure the SCIM application in the User Directory system, in this case, Okta.

Okta Configuration

  • Sign in to the Okta Portal
  • Select Applications, then ‘Browse App Catalog’
  • In the search bar, enter ‘SCIM’ and select ‘SCIM 2.0 Test App (Header Auth), then ‘Add Integration’
  • Provide a name in the ‘Application Label’ field under ‘General Settings’ and select ‘next’
  • Accept defaults on ‘Sign-On Options’ page & select ‘DONE’
  • Now navigate to the ‘Provisioning Tab’ and Select ‘Configure API Integration’, then tick ‘Enable API Integration’
  • In the ‘Base URL’, enter the URL saved from NEONNOW in earlier step
  • In the ‘API Token’, enter ‘bearer <APIKEY>’.  e.g. if your API key is ABC123, enter ‘bearer ABC123’ (without single quotes).
  • Now select ‘Test API Credentials’.  Below shows a screenshot of the successful test. Select ‘Save’
  • On the Provisioning tab, under ‘To App’ select ‘Edit’ and ensure the following tick-boxes are set:
  • Scroll down to ‘Attribute Mappings’ section, and ensure that the mapping are set exactly like below
  • Note you can also reference the SCIM mappings on the NEONNOW directory application, under ‘SCIM Attribute Mappings’ on page 2 of the directory wizard.
  • Now navigate to the ‘Assignments’ section’ and add an group or set of users.
  • This should trigger provisioning automatically.  Check Reports/System Log in Okta to check for any issues
  • External contacts should now load within the External Directory within NEONNOW. Note, you may be need to re-load NEONNOW interface if the directory did not exist when the contact was loaded.

Table of Contents
Go to Top