LogoLogo
WebsitePricingBlog
  • Debricked Documentation
  • Overview
    • Getting started
      • Create a OpenText Core SCA account
      • Running OpenText Core SCA
    • Help
      • Frequently asked questions (FAQ)
      • Upgrade your account
      • Get help in OpenText Core SCA tool
    • Language support
      • C# - Nuget, Paket
      • CycloneDX SBOM
      • Go - Go Modules, Go Dep, Bazel
      • Java & Kotlin - Gradle, Maven, Bazel
      • JavaScript - NPM, Yarn, Bower
      • Objective-C - CocoaPods
      • PHP - Composer
      • Python - Pip, Pipenv
      • Ruby - RubyGems
      • Rust - Cargo
      • Swift - CocoaPods
      • Linux package managers
      • Scala - SBT
    • Security overview
  • Product
    • Vulnerability management
      • Security terms
      • Data sources
      • See your data
      • Pull Requests (PR)
        • Enable Pull Request support
        • Solve vulnerabilities using Pull Requests (PR)
        • Solve vulnerabilities using Pull Requests (PR) via API
      • Set a review status
        • Snooze or pause a review status
      • Reachability Analysis
        • Set up Reachability Analysis for Java
        • Set up Reachability Analysis for Go
      • Solve vulnerabilities manually with root fixes
    • License risk management
      • Licence families
      • License risks
      • Set up a use case
        • Set up a use case using API
      • Proxy non-standard license identifiers
    • Project health
      • Contributors
      • Popularity
      • Security
    • Open source select
      • Search projects
      • Compare projects
      • View more details
      • Start left policies
      • OpenText Core SCA Select Browser Extension
      • End of Life (EOL)
    • Automation
      • Create an automation rule
      • Edit an automation rule
      • Default automation rules
      • Set up webhooks
      • Policies
      • Monitoring
    • Exporting or SBOM
      • Overview
      • License export
      • Vulnerability export
      • SBOM export
        • CycloneDX SBOM export
        • SPDX SBOM export
    • Administration
      • Generate access token
      • Account
        • Change your password
        • Delete your account
        • Delete company account
      • Billing
        • Manage contributing developers
        • Manage billing frequency
        • Manage payment methods
        • Access invoices
        • Manage your subscription
      • Settings
        • Enable and disable snoozing vulnerabilities
        • Supported language for Debricked tool
        • View logged events
        • Two-Factor Authentication (2FA)
      • Users
        • User roles (freemium and premium)
        • Role-Based Access Control (Enterprise)
        • Manage users
          • Add a new user
      • Repositories
        • Default Branch
        • Repository groups
        • Manually upload a dependency file
        • Manage your commits
  • Tools & Integrations
    • Command Line Interface (CLI)
      • Debricked CLI
        • High performance scans
        • File fingerprinting
      • Legacy CLI
    • CI/CD integrations
      • GitHub
      • CircleCI
      • BuildKite
      • GitLab
      • Bitbucket
      • Azure DevOps
      • Argo workflows
      • Travis CI
      • Jenkins
      • Bamboo
      • TeamCity
    • Fortify on Demand (FoD)
    • Fortify Software Security Center (SSC)
    • Debricked APIs
      • Open source select API
    • Integrated Development Environments (IDEs)
    • Single Sign-On (SSO)
      • Single Sign-On (SSO) through Okta
      • Single Sign-On (SSO) through Microsoft Entra ID
      • Single Sign-On (SSO) through JumpCloud OIDC
      • Single Sign-On (SSO) through GitHub
  • Tips & Tricks
    • Debricked CLI migration guide
    • Workarounds
      • Scanning Conan (C++) projects
      • Scanning a repository with different services
      • Scanning Docker images
      • Automations: Do not fail on found CVE lacking a fix
Powered by GitBook
LogoLogo

Company

  • Pricing
  • Blog

Support

  • Privacy Policy
  • Terms & Conditions
  • Service Status

Resources

  • Vulnerability DB
  • Open Source Select

© 2018-2024 | Open Text

On this page
  • Adding a new application
  • Configuring Debricked application
  • Communicating data with Debricked
  • Adding users
  • Testing setup

Was this helpful?

Export as PDF
  1. Tools & Integrations
  2. Single Sign-On (SSO)

Single Sign-On (SSO) through JumpCloud OIDC

Learn how to set up Single Sign-On (SSO) with Debricked through JumpCloud OIDC.

Last updated 2 months ago

Was this helpful?

This feature is currently only available for customers.

This article details how to configure JumpCloud OIDC as the primary Identity Provider to facilitate SSO with Debricked. For details regarding integration with other Identity Providers, see .

Adding a new application

  1. In your JumpCloud Admin portal, click SSO under User Authentication in the sidebar.

  2. Click + Add new application at the top of the page.

  3. Once the applications modal is open, click Custom OIDC App to start setting up the Debricked integration.

Configuring Debricked application

After clicking on Custom OIDC App you will be asked to name the new application. It is suggested to provide an easily recognizable name, for example, “Debricked” or “Debricked SSO”.

Select the SSO tab and complete the configuration:

  1. In the Redirect URIs input, set: *https://debricked.com/app/sso/oidc/auth*.

  2. The Client Authentication Type should be set to “Client Secret Basic”.

  3. Set the Login URL to: *https://debricked.com/app/sso/oidc/login*.

  4. Add three parameters to the Attribute Mapping section to enable Debricked to fetch the necessary user data. On the left, you can find the attribute names (make sure they are spelled correctly) and on the right the corresponding JumpCloud name. The mapping is as follows:

  • email → email

  • given_name → firstname

  • family_name → lastname

Now that everything is set up, you can click Activate at the bottom right of the page to save the application.

JumpCloud will now present you with the ClientID and Client Secret which you will need to send to Debricked support team to complete the integration.

Communicating data with Debricked

To complete the integration, enter the following information:

  • Issuer URL (the URL used to fetch OIDC information)

  • Email Domains (the email domains which will be designated to your organization)

  • Client ID (identifier of the Debricked integration)

  • Client secret (secret to authorize the integration, also provided when installing the integration in your IdP)

You can forward it to us by either:

  • Submitting the configuration data through an API endpoint at https://debricked.com/api/1.0/open/sso/oidc/request

Adding users

Note that in order for your users to be able to use this application you will need to assign them to the new application you have created. To do so, click the Debricked application from your JumpCloud Admin Portal and go to the User Groups tab, from here you will be able to assign user groups to this application

Testing setup

Once your integration has been added to your enterprise account, you can enable it in the Debricked web tool by visiting the User Permissions tab in Admin Tools.

Getting in touch with the support team at

Once your users are added, they can direct log in from . You can also invite them from Debricked (keep in mind that they must be assigned to the application on your vendor side) from your Admin Tools. This invite will be a special SSO invite, which will redirect them to your Identity Provider and let them log in to Debricked.

Head over to , type enterprise email ID (the same email domain which you submitted before). You should be redirected to your Identity Provider and be able to authenticate. After logging in, you will be redirected and logged in to Debricked as well.

SCA Enterprise
Single Sign-On (SSO)
support@debricked.com
https://debricked.com/app/sso/login
https://debricked.com/app/sso/login