Graylog2 / Graylog2/graylog2-server

Require streams selection when creating an event definition

Open
#9,581 1 comment 1 reaction 0 assignees View on GitHub
feature
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## What?
The streams select is currently optional, when creating an event definition.
![image](https://user-images.githubusercontent.com/46300478/99966985-7cadab00-2d97-11eb-9f4f-382994df94b5.png)

If a user does not have access to all streams and leaves this field empty, the POST which creates the event definition results in a 403.

## Why?
We should require the streams selection to ensure a user is able to create an event definition and to avoid the following scenario:
1. User creates an event definition with a filter which does not include any stream
2. New inputs and streams get configured
3. Filter for the event definition also includes new inputs / streams, even though it probably should not

## Your Environment

* Graylog Version: 4.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.