Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Cancelling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
        • Tests Performance
      • Spec Files Explorer
        • Spec Files Performance
      • Errors Explorer
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • Supported features
  • Requirements
  • Configuration Steps
  • JumpCloud Configuration
  • Known Issues/Troubleshooting

Was this helpful?

  1. Administration
  2. SSO SAML2.0
  3. JumpCloud

JumpCloud User provisioning

Provision and de-provision users in Currents using JumpCloud

PreviousJumpCloudNextOkta

Last updated 22 days ago

Was this helpful?

Supported features

  • Create users - JIT provisioning when they first login to Currents.

  • Update user attributes - accept name updates for users.

  • Deactivate users - prevents the user from logging into Currents, deactivated users are removed from the Currents team member list.

  • Import users - Link your existing Currents users to their JumpCloud user.

For more information on the listed features, visit the .

Requirements

Provisioning is available for customers with an active subscription.

In order to setup provisioning you first need to:

  • Setup the SAML integration with JumpCloud

  • Reach out to the Currents support team to have provisioning enabled for your organization.

Configuration Steps

Currents Configuration

  • Login as an Admin and navigate to the Manage Team page.

  • Click the Show SCIMv2 Details button in the DOMAIN ACCESS & SSO section of the page.

  • Note the Endpoint and Token details for JumpCloud Configuration

JumpCloud Configuration

  • Navigate to the existing Currents SSO Application in JumpCloud USER AUTHENTICATION > SSO Applications. Click on the Currents SSO Application you previously setup.

  • Select the Identity Management tab. Then provide the Base URL (Endpoint) and API Token information from Currents. Also enter a Test User Email that does not already exist in Currents.

  • Click Test Connection and verify it was successful.

  • If everything was succeful, click Save

  • Navigate to the Current SSO App again, and back into the Identity Management Tab

  • Use the manual import button to find your existing Currents accounts

Known Issues/Troubleshooting

Unsupported Features

The Currents User Provisioning does not support the following JumpCloud Identity Management features:

  • Group Management

  • Sync password

Limited profile attributes updates

Currents does not accept updates to the following attributes:

  • userType - changing a user's role is only supported from the Currents team member dashboard

  • userName - the mapped userName must match the primary email

  • email - the primary email cannot be changed

Username errors on import

JumpCloud attempts to use the first part of the email as the username when importing new users from Currents. (eg, andrew@currents.dev becomes andrew )

If your users have a + character in their email, the import will fail. To workaround, first create the user in JumpCloud, then sync them with Currents. JumpCloud and Currents will sync based on the user email.

User Activation Error

Toggle off Group Management and click Activate to verify the .

Your existing users should have been auto-matched based on email. If there are any additional Currents users that failed to be matched, you can import them from the import screen. (See )

When setting up Identify Management in JumpCloud, you must use a new user as the test email, otherwise you get errors during the test. This is referenced in .

JumpCloud Support Page
default mappings
JumpCloud's Importing Users Guide
JumpCloud's SCIM Important Considerations
Navigate to the Manage Team page
Getting the SCIM details from the Manage Team page
Navigate tot he Currents App
Configure and Test the API Credentials
Import Users