Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read-only user unable to view logs of an event for which Category was changed #785

Open
1992kk opened this issue Jul 15, 2024 · 1 comment

Comments

@1992kk
Copy link

1992kk commented Jul 15, 2024

Summary

Read-only user unable to view logs of an event for which Category was changed.

Steps to reproduce the problem

  1. Change category of an existing event from let's say "A" to "B"
  2. Create a read-only user limited to category "B"
  3. Try to view event history logs of the event.

Your Setup

Operating system and version?

Rocky linux 8.7

Node.js version?

v16.19.1

Cronicle software version?

0.9.53

Are you using a multi-server setup, or just a single server?

1 master, 3 workers

Are you using the filesystem as back-end storage, or S3/Couchbase?

filesystem

Can you reproduce the crash consistently?

Yes

Log Excerpts

Error: User 'xxx' does not have the required account privileges to perform this action (cat_clpvmb0mj23).

@jhuckaby
Copy link
Owner

I cannot reproduce this issue. I followed the steps exactly. My new underprivileged user which was limited to the new category can view the event history and the job logs in that category no problem.

Try refreshing your browser maybe? Perhaps the category or user data got stuck in the cache?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants