Creating Client Secrets

Prerequisites

Before creating a client secret, ensure you have:

  • The Security Manager role or higher in the organization
  • Determined the required access level (Viewer or Contributor)
  • Planned the secret’s lifetime and analytics requirements

Creation Process

  1. Navigate to your organization’s settings:
    • Go to Organizations
    • Select your organization
    • Click Settings
    • Select Client Secrets

Navigation to client secrets

Click the image to enlarge

  1. Click “Create Client Secret”

Create new  client secrets

Click the image to enlarge

  1. Complete the configuration form:

    • Description: Enter a meaningful name (max 255 characters)
    • Role: Select access level
      • Viewer: For read-only operations
      • Contributor: For read and write operations
    • Analytics Mode: Choose data collection level
      • Disabled: No analytics
      • Limited: Basic metrics only
      • Complete: Full usage data
    • Expiration: Set validity period (1-24 months)

Create new  client secrets form

Click the image to enlarge

  1. Review and confirm the settings

  2. Save the client secret

Create new  client secrets form

Click the image to enlarge

Configuration Details

Description

  • Serves as an identifier for the secret
  • Maximum length: 255 characters
  • Should be descriptive and meaningful
  • Examples: “GitHub Actions Deployment”, “Azure DevOps Pipeline”

Role Options

  • Viewer
    • Download packages
    • Sync workspaces
    • View package information
  • Contributor
    • All Viewer permissions
    • Create new packages
    • Update existing packages

Analytics Modes

  • Disabled
    • No usage tracking
    • Minimal logging
  • Limited
    • Basic operation logging
    • Usage patterns
  • Complete
    • Full feature usage tracking
    • Detailed analytics

Expiration Settings

  • Minimum: 1 month
  • Maximum: 24 months
  • Set in monthly increments
  • Default: 24 months

After Creation

After creating a client secret:

  1. Copy the generated secret value immediately
  2. Store it securely in your automation platform
  3. Test the secret with minimal permissions first
  4. Document where and how the secret is used