Opened 17 years ago
Closed 17 years ago
#770 closed defect (fixed)
Filter plug-in is lacking permission to read reporter lists
Reported by: | Johan Vallon-Christersson | Owned by: | Martin Svensson |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.4.2 |
Component: | coreplugins | Version: | |
Keywords: | Cc: |
Description
Trying to run a filter that use my own Reporter list. Get error: "Permission denied: Not allowed to read Reporter list[id=1; name=Pick method(1.%]"
Change History (7)
follow-up: 3 comment:1 by , 17 years ago
Component: | web → coreplugins |
---|---|
Milestone: | BASE 2.x+ → BASE 2.4.2 |
Summary: | Not allowed to read my own Reporter list → Filter plug-in is lacking permission to read reporter lists |
comment:2 by , 17 years ago
Browsing through the jobs I notice that this is the problem occurs with JEP filter plugin. There is no restriction on always read/deny. The plugins on the server is run through a jobagent, could this be causing the problem (jobagent does not have enough credentials)?
comment:3 by , 17 years ago
I can verify that the plugin lacked permission to read reporter list. Changed the permissions and now it woks perfectly. Problem solved.
follow-up: 5 comment:4 by , 17 years ago
Shouldn't the JEP filter plugin come properly configured out-of-the-box?
comment:5 by , 17 years ago
I agree that it is logical to have the filter plugin configured (out-of-the-box) to allow reading reporter lists.
comment:6 by , 17 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:7 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I think it is the plug-in you are running that lacks permission to the reporter list. Can you verify this?
If that is the case, it can easily be fixed by giving the plug-in more permissions.