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
  • Registering a new Microsoft Entra ID application
  • Getting client ID
  • Getting OIDC metadata endpoint (issuer URL)
  • 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 Microsoft Entra ID

Learn how to set up Single Sign-On (SSO) with Debricked through Microsoft Entra ID.

Last updated 2 months ago

Was this helpful?

This feature is currently only available for customers.

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

Registering a new Microsoft Entra ID application

  1. Search for App registrations.

  2. Click New registration. It is suggested to name your application “Debricked”, but it is not mandatory.

  3. In the Redirect URI, section select Web as type of application and enter:

  1. Confirm the details and proceed to the next step.

Getting client ID

You can find the Client ID from the Overview section, the first page you will see after creating the application.

Creating Client Secret

  1. On the sidebar, click Certificates & secrets.

  2. Click New client secret and choose a name and expiration date. When it is created, ensure to copy and store somewhere, as it will only be visible once.

Getting OIDC metadata endpoint (issuer URL)

This is needed for Debricked to know where to redirect the user, fetching credentials tokens and fetching user information.

  1. Go back to the Overview from the sidebar and click Endpoints tab.

  2. The one needed is called the OpenID Connect metadata document.

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 added.

  1. Go to Enterprise applications.

  2. Click on your Debricked application and then go to Users and groups. Here, you will be able to assign users and user groups.

Testing setup

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

Getting in touch with the support team at

Once your users are added, they can directly log in from . You can also invite them from Debricked (note 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 into Debricked.

You can head over to , input the enterprise email (with the same email domain which you submitted), and you will be redirected to your Identity Provider to authenticate. After logging in, you will be redirected and logged into Debricked.

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