All articles

Wrike & OneLogin: User Provisioning

Wrike admins on Enterprise accounts can set up automatic user provisioning and deprovisioning for Wrike with OneLogin using SCIM protocol.

⏱ 3 min read

Overview

Set up Wrike with the System for Cross Identity Management (SCIM) standard to automatically provision or deprovision users based on their status in OneLogin.

Set Up Wrike with SCIM to Use:

  • Automatic provisioning - OneLogin users are automatically provisioned for Wrike.
  • Synced User Attributes - User attributes are automatically updated in Wrike when they are updated in OneLogin. View synced attributes.
  • Automatic deactivation - Wrike users are automatically deactivated in Wrike when they are deactivated in OneLogin.

This page is about integrating Wrike with OneLogin SCIM, we have a separate page on how to set up SSO with SAML.

Important Information

  • Members added through SCIM are billable as soon as they're provisioned.

Set Up Wrike with OneLogin SCIM

You must be an admin on a Wrike Enterprise account with the permission "Configure advanced security settings" as well as a OneLogin admin to set up Wrike with OneLogin SCIM. We recommend setting up SSO with SAML before proceeding.

Step 1: Add Approved Domains

Check out help page for how to add approved domains. Only users from approved domains will be automatically provisioned to Wrike.

Step 2: Find and Note the SCIM URL

  1. Open your Wrike Workspace.
  2. Click your profile picture in the view’s upper right-hand corner.
  3. Select Apps & Integrations.
  4. Click “Configure” next to OneLogin.
  5. Go to the SCIM tab.
  6. Copy the URL (displayed at the bottom of the pop-up) and save it somewhere. You’ll be using it in a few steps.
  7. Close the OneLogin pop-up (but stay in Wrike) and proceed to step 3.

Step 3: Obtain the OAUTH Token

  1. Click API from the left-hand side of the Apps & Integrations page.
  2. Enter a name in the “App name” field (we suggest OneLogin SCIM).
  3. Click “Create new”.
  4. Add an app description (optional).
  5. Scroll to the bottom of the page and click “Obtain token”.  
  6. Copy the token and save it somewhere, you’ll need to enter this information in OneLogin.

Important! You’re only shown your token once, so make sure you save it somewhere.

Step 4: Finalize the Setup from OneLogin

  1. Sign in to your OneLogin domain at <yourorganization>.onelogin.com.
  2. Click Administration.
  3. Click Apps and select Company apps.
  4. Find and select “Wrike”.
  5. Switch to the "Configuration" tab.
  6. Add information
    • In the SCIM Base URL field - add the url obtained in Step 2.
    • In the SCIM Bearer Token field - add the token obtained in Step 3.
  7. Click “Enable” next to API status.
  8. Select the "Provisioning" tab.
  9. Select "Enable provisioning for SCIM Provisioner with SAML (SCIM v2)”.
  10. (optional) Specify if approvals are required and what should happen in case a user is deleted from OneLogin.
  11. Click Save.
  12. Ensure that any user/group who should be is assigned for Wrike.

Synced Attributes

The following attributes are synced from OneLogin to Wrike:

  • Username
  • Given name
  • Family name
  • Primary email
  • Job Title
  • Primary phone number
  • Organization name
  • Department
  • wrikeUserType*

*This is a custom attribute, specifying the type of user in Wrike. Supported values: "Regular", "External" and "Collaborator". By default, Regular Users are created.

Troubleshooting

Missing Attributes

If certain user attributes (e.g. phone number, department, or secondary emails) are filled in in Wrike but missing in OneLogin, the information remains in Wrike even after user provisioning.

User Provisioning/Deprovisioning

If a user does not get provisioned or deprovisioned,

  1. Check the System Log in the OneLogin administration portal to see if a SCIM provisioning attempt is listed there.
    • If there is no provisioning attempt listed, make sure that users are properly assigned to Wrike’s application in OneLogin.
    • If an error is listed, please contact our Support Team (support@team.wrike.com) and provide error details.
0 comments

Article is closed for comments.

Top