Skip to main content
Skip table of contents

Set Up Okta Provisioning with Declaree via SCIM

This guide explains how to configure Okta provisioning with Declaree using SCIM.


Requirements

Before you start, make sure the following requirements are met:

  • Create a dedicated user account in Declaree with admin rights.
    If you have more than one organization, add this account to the parent organization (the default organization for provisioned users).

  • To sync groups successfully, ensure that each group name is unique. Duplicate group names will not be linked.


Step 1: Retrieve Information from Declaree

  1. Log into your Declaree instance as an admin (preferably using the dedicated account).

  2. Navigate to My Account → (click your name in the top-right corner).

  3. Go to the Declaree API tab.

  4. Click Generate Key and copy the generated key. You’ll need this later.

image-20250909-120758.png

Step 2: Configure Okta

  1. Log into your Okta instance as an administrator.

  2. Navigate to Applications → Applications.

  3. Select the Declaree application.

General Tab

  1. Go to the App Settings section.

  2. Click Edit.

  3. Select the SCIM option for provisioning.

  4. Click Save.

Provisioning Tab

  1. Click Edit.

  2. In SCIM connector base URL, enter:

  3. In Unique identifier field for users, enter:

    • userName

  4. In Authentication Mode, select HTTP Header.

  5. In Authorization, paste the API key you generated in Step 1.4.

  6. Click Test Connector Configuration.

    • If successful, click Save.

Step 3: Enable Provisioning Actions

In the Provisioning tab, you can now:

  • Enable actions such as Create Users and Update User Attributes.

  • Map Declaree attributes with Okta attributes.

👉 Note: We recommend disabling import from Declaree to Okta, as all user management should occur from Okta.


Step 4: Assign Users in Okta

  1. Go to the Assignments tab.

  2. Add users to the Declaree application.

Your Okta provisioning with Declaree is now configured.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.