Revspire Resources

OneLogin SCIM Provisioning

The OneLogin SCIM integration provisions and deactivates Revspire users and groups from your OneLogin tenant.

Before You Start

  • OneLogin administrator access.
  • A tested Revspire SAML application or a OneLogin SCIM Provisioner with SAML connector.
  • An active Revspire Deal Room entitlement for the Revspire organization.
  • Revspire access to Setup > SSO with View SSO Settings, Edit SSO Providers, and Generate API Tokens permissions.
  • A default internal profile unless OneLogin sends an explicit profile mapping, plus an eligible default product when users should be created active.

Step 1: Copy Revspire SCIM Values

In Revspire > Setup > SSO, select the OneLogin provider and click SCIM Config.

SCIM Base URL = <copy from Revspire>
SCIM Bearer Token = <generate and copy once>

Step 2: Use a SCIM-Enabled OneLogin Connector

Select the Revspire application in OneLogin Admin > Applications > Applications.

If the existing SAML-only custom connector has no Provisioning, SCIM Base URL, or API Connection controls, select the OneLogin SCIM Provisioner with SAML variant that uses SCIM v2 Core Schema and Bearer-token authentication. Exact catalog suffixes vary by OneLogin edition. Copy the tested Revspire SAML settings into that connector.

Step 3: Configure the SCIM Connection

Path: Revspire Application > Configuration

OneLogin Field Label: SCIM Base URL
Value: <Revspire SCIM Base URL>

OneLogin Field Label: SCIM JSON Template
Value: leave blank to use the OneLogin Core User Schema

OneLogin Field Label: Custom Headers
Value: leave blank for the public Revspire HTTPS endpoint

OneLogin Field Label: SCIM Bearer Token
Value: <Revspire SCIM Token only>

Save, then click Enable. Confirm that OneLogin shows API Status: Enabled before provisioning users.

Step 4: Verify Parameters and Emitted Attributes

Path: Revspire Application > Parameters

OneLogin username / email login -> userName
OneLogin Email -> emails[type eq "work"].value
OneLogin First Name -> name.givenName
OneLogin Last Name -> name.familyName
OneLogin immutable user ID -> externalId
OneLogin lifecycle state -> active

OneLogin parameter labels vary by connector edition. Use its request preview or provisioning log to verify the SCIM target attributes above rather than relying only on the source-field label.

Use the Revspire default profile unless your connector is deliberately configured to send the Revspire profile extension.

Step 5: Enable Provisioning

Path: Revspire Application > Provisioning

  1. Enable provisioning.
  2. Enable user creation, attribute updates, and deactivation according to your approval workflow.
  3. Keep password synchronization disabled.
  4. Scope the application to one test user before enabling a production population.

Step 6: Test Users and Groups

  1. Provision one user whose username and work email are not already used in Revspire.
  2. Confirm the expected profile, product, active state, and license assignment.
  3. If your OneLogin connector supports SCIM group objects, enable group provisioning and test a small group after its users exist.
  4. If the connector provisions only users, manage groups separately or use a connector edition that supports SCIM v2 Groups.

Troubleshooting

  • 401: verify the exact base URL, Bearer header, selected provider, and token status. Rotate only when the token is expired, revoked, or unavailable.
  • 409: resolve the reported uniqueness conflict or unavailable product seat; Revspire does not overwrite another resource.
  • 422: verify the default internal profile, default product, organization defaults, and product dependencies.
  • No provisioning controls: the selected OneLogin connector is SAML-only; select a SCIM-enabled connector.

See the SCIM Provisioning overview for supported operations and lifecycle rules.