Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9393

Closed
Open
Created Jun 16, 2015 by Administrator@rootOwner

Recommended approach for a client to receive notifications

Created by: valeriomazzeo

What would be the best way to provide 3rdparty client's users with notifications?

In theory it should be possible to set up some project(s) Web Hooks and send them to a centralise server (managed by the 3rdparty client owner) that can then dispatch notifications to the appropriate clients.

gitlab -> notification server -> clients

However, there can be many gitlab hosts where people can connect to and this makes it impossible for the notification server to be able to find out the correct set of registered clients that should receive such notifications.

Each client may register for a defined host after login, but hosts may not be unique. For example someone may host gitlab on a private network 192.168.0.1 and that hostname may collide with someone else.

It should be possible to secure the incoming connection side of things using OAuth2 registering the host to the notification server which can then return an auth token to use in the web hook, but still it wouldn't be enough for it to match the corresponding users.

It would be interesting to know what are your thoughts and how this could be achieved.

Thanks.

Assignee
Assign to
Time tracking