You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.
When I add read permission for particular Pipeline rule to role by REST API, user with that role isn't able to manage this Pipeline rule. Page http://<Graylog_node>:9000/system/pipelines/rules isn't available. User get error
Could not retrieve processing rules
Fetching rules failed with status: cannot GET http://<Graylog_node>:9000/api/plugins/org.graylog.plugins.pipelineprocessor/system/pipelines/rule (403)
Steps to reproduce the problem
Make sure you have at least one Pipeline rule
Create role with read permission for one Pipeline rule and without permission to read all Pipeline rules. Created role must contain line like this in the permission list:
"pipeline_rule:read:<Pipeline_rule_ID>",
And this role shouldn't contain line:
"pipeline_rule:read",
Add user to created role
Try to open page http://<Graylog_node>:9000/system/pipelines/rules by created user
Environment
Graylog Version: v2.4.6+ceaa7e4
Pipeline Processor plugin version: 2.4.6
Elasticsearch Version: 5.6.10
MongoDB Version: v3.6.6
Operating System: Debian 9
Browser version: Chrome 69
The text was updated successfully, but these errors were encountered:
valihanov
changed the title
Read permissions per pipeline rule
Problem with read permissions per pipeline rule
Oct 16, 2018
Problem description
When I add read permission for particular Pipeline rule to role by REST API, user with that role isn't able to manage this Pipeline rule. Page http://<Graylog_node>:9000/system/pipelines/rules isn't available. User get error
Steps to reproduce the problem
And this role shouldn't contain line:
Environment
The text was updated successfully, but these errors were encountered: