CodeThreat - Knowledge Center
CodeThreatGithub
  • Latest
    • v2409 Cloud Upgrades, Repo Monitoring, Path Exclusion, and New JS/TS Rulesets
  • Product Updates
    • v2402 GenAI, Sarif and New Language Supports
    • v2401 SCA Release
    • v2311.30
    • v2310.29
    • v2309.30
    • v2308.30
    • v2307.25
    • v2306.26
    • v2305.26
    • v2304.23
  • Privacy Policy
  • Terms of Service
  • Company Handbook
  • Usage Guide
    • API Documentation
    • CT Server Installation
      • Deploy with Docker
      • Self-Hosted Server Setup
      • Installation
    • Introducing CodeThreat
    • Create a CodeThreat Account
    • Quick Start & Scan
    • HomePage
    • Projects
      • Overview
      • Scans
      • SCA(Software Composition Analysis)
      • Licences
      • Dependency Tree
      • Project Structure
      • Report
    • Issues
      • Issue List
      • Issue List Filter
      • Issue Detail
    • Integrations
      • Azure
      • Github
      • Gitlab
      • Jira
    • CI-CD Integrations
      • GitHub Actions
      • Jenkins
      • Gitlab
      • Bamboo
      • Azure
    • Notifications
    • Settings
      • General
      • SMTP
      • License
      • OAUTH Apps
        • Azure
        • Github
        • GitLab
      • Organizations
      • Scan Policy
      • Users & Groups
      • Notifications
      • Access Token
Powered by GitBook
On this page

Was this helpful?

  1. Usage Guide
  2. Settings
  3. OAUTH Apps

GitLab

Client ID

  • Description: This identifier is unique to your OAUTH application on GitLab.

  • Instructions:

    1. Go to your GitLab OAUTH application settings.

    2. Locate and copy the Client ID.

    3. Paste the Client ID into the respective field on the integration page.

Client Secret

  • Description: This is a confidential key associated with your GitLab OAUTH application.

  • Instructions:

    1. In the GitLab OAUTH application settings, find the Client Secret.

    2. Copy and paste the Client Secret into the designated field.


3. Callback URL Configuration

  • Description: This URL is where GitLab will redirect users after they have granted or denied permission for your OAUTH application.

  • Instructions:

    1. In your GitLab OAUTH application settings, set the Callback URL to align with the example provided, ensuring a consistent path.

    2. The URL should adhere to the format: https://[your-domain].com/settings/integration-settings/gitlab.

PreviousGithubNextOrganizations

Last updated 1 year ago

Was this helpful?