Graylog2 / Graylog2/graylog2-server

Permissions that should be configurable

Open
#3,482 5 comments 2 reactions 0 assignees View on GitHub
feature triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

I found no issue where something like a list of missing permission configuration options are listed.

Here is my list of which permission options i miss:

- System Menu access (more granularity)
- Alerts and Conditions (more granularity)
- Stream and Dashboard editing needs more granularity (start, stop, alert, rules, index sets, remove messages from default stream ...)
- API Access (In general to allow every API only via Authentication)

## Context
At the Moment our Non-Admin users can see too much of the internals, and maybe misconfigure something when i grant them edit permissions. So we have to do all small changes, like Alert adding and Dashboard Building/Changing via an Admin.

## Your Environment
Graylog 2.2.0+d9681cb on syslog.xyz.local (Oracle Corporation 1.8.0_121 on Linux 3.10.0-327.22.2.el7.x86_64) [footnote: THX for the great 2.2 release!!]

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.