Open Stack

Hi Eric,

In Monasca use cases sending the token in the request header should be enough, I guess. I'm adding the references to the HipChat [1] and Slack APIs [2] as well as two old blueprints [3, 4].

[1] https://developer.atlassian.com/server/hipchat/about-the-hipchat-rest-api/
[2] https://api.slack.com/web#authentication
[3] https://blueprints.launchpad.net/monasca/+spec/webhook-api-support
[4] https://blueprints.launchpad.net/monasca/+spec/secure-notification-params

Greetings
Witek

P.S. Adding Vitrage to the tags list.


> -----Original Message-----
> From: Eric K <ekcs.openstack at gmail.com>
> Sent: Donnerstag, 3. Mai 2018 21:50
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev at lists.openstack.org>
> Subject: [openstack-dev] [keystone][monasca][congress][senlin][telemetry]
> authenticated webhook notifications
> 
> Question to the projects which send or consume webhook notifications
> (telemetry, monasca, senlin, vitrage, etc.), what are your
> supported/preferred authentication mechanisms? Bearer token (e.g.
> Keystone)? Signing?
> 
> Any pointers to past discussions on the topic? My interest here is having
> Congress consume and send webhook notifications.
> 
> I know some people are working on adding the keystone auth option to
> Monasca's webhook framework. If there is a project that already does it, it
> could be a very helpful reference.