Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #361216
Closed
Open
Issue created May 03, 2022 by Max Woolf@mwoolf2️⃣Maintainer

Create streaming audit event headers

Overview

Currently, when streaming audit events, GitLab adds a single HTTP header to aid in verification but group owners cannot specify their own HTTP headers.

Certain ingestion services require certain header values for authentication or other purposes.

Proposal

  • Create a new model that represents a HTTP header.
  • Create a 1-M association between audit streaming destinations and headers. (This should have a limit per group, 20 perhaps?)
  • Create a new GraphQL mutation to create a header for a destination. Something like:
mutation {
  externalAuditEventDestinationHeaderCreate(input: { desintationID: "gid://gitlab/somethingsomething/Destination/2, key: "Authorization", value: "Bearer thisisatoken" } ) {
    errors
  }
}
  • Update the audit streaming worker to include those headers.
Edited May 06, 2022 by Max Woolf
Assignee
Assign to
Time tracking