LogoLogo
WebsiteBlog
  • OpenText Core Software Composition Analysis (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
      • Configuring user access using API
Powered by GitBook
LogoLogo

Company

  • Blog

Support

  • Privacy Policy
  • Service Status

Resources

  • Vulnerability DB
  • Open Source Select

© 2018-2024 | Open Text

On this page

Was this helpful?

Export as PDF
  1. Tips & Tricks
  2. Workarounds

Configuring user access using API

Learn how to configure user access using API.

Last updated 1 day ago

Was this helpful?

We can update user roles for a repository by using the API endpoint: ''. This endpoint allows us to assign roles to multiple users at the same time for the repository.

When assigning roles to multiple users, each user will receive the same set of roles for the specified repositories.

Sample script

Let us consider a scenario where we want to assign the Company Admin role (roleId=6) to a repository (id=5) and remove the Repository Admin role (roleId=5) from the same repository (id=5). We intend to apply this change to multiple users, specifically user ID 1125.

In the payload of the API, there are 3 main sections:

  1. userIds

    1. An array of user IDs

    2. All the users in the array will receive or lose the same set of role or repo mapping.

  2. Access

    1. Type: Array

    2. This field can be used to provide role access to a certain repository.

    3. Each array item will contain a repo ID and a role ID.

  3. noAccess

    1. Type: Array

    2. This field can be used to revoke role access to a certain repository.

    3. Each item in an array will contain a repoId and roleId.

Note:

  1. To get the repository IDs, you can use the below API endpoint: api/{version}/open/repositories/get-repositories-names-links

  2. To get the user ID, use /api/{version}/open/admin/users

  3. To get the role ID, there is no endpoint at the moment. Refer the following table to get the ID:

Roles
ID

Viewer

1

Repository Admin

5

Company Admin

6

Developer

2

Maintainer

4

Reviewer

3

https://debricked.com/api/1.0/open/admin/rbac/update-user-roles-by-repo