3 Commits

Author	SHA1	Message	Date
Nazar Gargol	60ae9e82f9	Fixed integration_id assignment for webhook when creating through API key auth ... refs 173e3292fa - The bug was initially introduced in referenced commit. When request is done with `api_key` context, there should always be an `integration` object associated with it - 71c17539d8/core/server/services/permissions/parse-context.js (L36) . An `id` from `context.integration` not `context.api_key` has to be assigned to newly created webhook! - The webhooks API is about to be declared stable in upcoming release, so no migration will be done	2020-08-04 16:43:24 +12:00
Nazar Gargol	1b449f4f53	🐛 Fixed 500 error in webhooks API when modifying non-existing webhooks ... closes #12064 - Handled permission check bug by returning 404, same way it is returned in other permissions related places when handling non-existing resource. Example - 60907a7ae4/core/server/models/relations/authors.js (L355-L358)	2020-08-03 23:08:47 +12:00
Nazar Gargol	173e3292fa	Fixed integration_id handling in Webhooks Admin API ... no issue - Changes introduced to both API v3 and v2 - Makes sure to use the same integration_id as authenticated integration for the webhook's data. - Makde it is impossible to create orphaned webhooks using token authentication - Allowed only parent integration to edit it's children webhooks. Throwing permission error otherwise	2020-07-08 16:54:31 +12:00