LogoLogo
WebsitePricingBlog
  • OpenText Core Software Composition Analysis (OpenText Core SCA) 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 OpenText Core SCA 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)
      • OpenText Core SCA 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)
    • OpenText Core SCA 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
    • OpenText Core SCA 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
  • Set up SSO using Open ID Connect (OIDC)
  • Log in to OpenText Core SCA using SSO

Was this helpful?

Export as PDF
  1. Tools & Integrations

Single Sign-On (SSO)

Learn how to set up Single Sign-On (SSO) with OpenText Core SCA through an Identity Provider of your choice.

Last updated 3 days ago

Was this helpful?

This feature is currently only available for customers.

This article details the general configuration with an Identity Provider to facilitate SSO with OpenText Core SCA. For details regarding integrations with specific providers, see:

Integrating your Single Sign-On provider with OpenText Core SCA allows for a more streamlined user experience, simplifying user management and enhancing security. You can authenticate with your SSO provider to access the tool, eliminating the need to create and remember separate login credentials. This integration also helps to ensure that access to the OpenText Core SCA tool is only granted to authorized users, as authentication is handled by the SSO provider.

To be able to complete the integration, upgrade to the Enterprise tier and get in touch with OpenText Core SCA support team at

Set up SSO using Open ID Connect (OIDC)

Using OIDC requires an exchange of parameters between your company and OpenText Core SCA. To set up the integration at your Identity Provider, you need to enter the following parameters:

Parameter
Value

Callback/Redirect URI

https://debricked.com/app/sso/oidc/auth

Sign-out redirect URI

https://debricked.com/app/en/logout

IdP Initiated URI (if supported by provider)

https://debricked.com/app/sso/oidc/login

OAuth Grant Type

Authorization code

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 OpenText Core SCA 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

Log in to OpenText Core SCA using SSO

  1. In the next step, type your email address, and complete the authentication with your SSO provider.

Getting in touch with the support team at

Once the integration is completed, you can log into Debricked by clicking Login with company SSO on the .

support@debricked.com
login page
SCA Enterprise

support@debricked.com

Single Sign-On through Okta
Single Sign-On through Microsoft Entra ID
Single Sign-On through JumpCloud OIDC
Single Sign-On through GitHub