Closed Bug 1659599 Opened 4 years ago Closed 3 years ago

[WEBHOOKS] Implement authentication token in Webhooks

Categories

(bugzilla.mozilla.org :: Extensions, enhancement)

enhancement

Tracking

()

RESOLVED FIXED

People

(Reporter: lisset.cuevasj, Assigned: dkl)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

Work on this as the last item if time allowed. Talked with manager and this feature is not as critical as others.

(In reply to David Lawrence [:dkl] from comment #1)

Work on this as the last item if time allowed. Talked with manager and this feature is not as critical as others.

Ok, don't worry, I'd like to continue contributing to the project now that the intership ended :)

And about this, Should it be a parameter in the body or something in the header as the spark_api_key in the Spark Connector?

(In reply to Lisset Cuevas from comment #2)

(In reply to David Lawrence [:dkl] from comment #1)

Work on this as the last item if time allowed. Talked with manager and this feature is not as critical as others.

Ok, don't worry, I'd like to continue contributing to the project now that the intership ended :)

And about this, Should it be a parameter in the body or something in the header as the spark_api_key in the Spark Connector?

IMO it should always be part of the header and never in the body or the query string. So for our case, we would new two fields
for the user to configure in the webhook. A field that is the actual header that will be included. In the case of BMOs API we accept
a header called X-Bugzilla-API-Key for example. And we need a second config field called key or something similar that is the
actual key or token to be passed. If either of those two fields are left blank, we just send the POST to the URL without the header
included as an anonymous client.

dkl

Summary: Implement authentication token in Webhooks → [WEBHOOKS] Implement authentication token in Webhooks
Blocks: 1588660
Assignee: nobody → dkl
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attached file GitHub Pull Request
Attached file GitHub Pull Request
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

Reopening as need to do a schema only push first.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Original commit reverted. Schema changes merged to master
https://github.com/mozilla-bteam/bmo/commit/fe22350a10856fa30a6e23744da5931513002606

Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: