starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

user permission take too long to reflect #4904

New Issue
Closed
opened 2025-12-29 19:21:58 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:21:58 +01:00
Owner
Copy Link

Originally created by @kaalbhairava on GitHub (May 12, 2021).

NetBox version

v2.11.3

Python version

3.6

Steps to Reproduce

  1. go to admin page
  2. go to users
  3. select an existing user
  4. change the permission (custom read-write permission to custom read-only permission)
  5. save

Expected Behavior

user should be able to view only what is given in read-only permission

Observed Behavior

user still has the read-write permission and permission changes don't reflect immediately.

Originally created by @kaalbhairava on GitHub (May 12, 2021). ### NetBox version v2.11.3 ### Python version 3.6 ### Steps to Reproduce 1. go to admin page 2. go to users 3. select an existing user 4. change the permission (custom read-write permission to custom read-only permission) 5. save ### Expected Behavior user should be able to view only what is given in read-only permission ### Observed Behavior user still has the read-write permission and permission changes don't reflect immediately.
adam added the type: bug label 2025-12-29 19:21:58 +01:00
adam closed this issue 2025-12-29 19:21:59 +01:00
adam commented 2025-12-29 19:21:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 12, 2021):

User permissions take effect immediately. I'm not able to test your reported issue because the steps you've provided above are not sufficiently detailed. Please revise your post above to state exactly what you are doing at each step, starting with the initial user creation.

@jeremystretch commented on GitHub (May 12, 2021): User permissions take effect immediately. I'm not able to test your reported issue because the steps you've provided above are not sufficiently detailed. Please revise your post above to state _exactly_ what you are doing at each step, starting with the initial user creation.
adam commented 2025-12-29 19:21:59 +01:00
Author
Owner
Copy Link

@kaalbhairava commented on GitHub (May 12, 2021):

Apology for not providing the exact details.
Following are the steps I performed from Netbox Administration Page:

  1. Created a user named TestUser1
  2. Created two permissions-
    ReadOnly - only view action is enabled for all objects
    ReadWrite - view, add, change, delete actions are enabled for all objects
  3. ReadWrite permission is given to TestUser1 after creation.
  4. After logging in as TestUser1 in Netbox , the given permission is getting reflected and I can perform view, add, change, delete actions
  5. Now, I went to Administration console and changed the permission of TestUser1 to ReadOnly
  6. Now, I again logged in as TestUser1, but I could still add IPAddresses and prefixes. After 20-30 mins the permission changes were reflected on the front end and now I could only view.
  7. After troubleshooting further, I found that the permission changes are getting reflected in database immediately (verified by querying the tables ), but not on the front end

** suspecting that somewhere something is getting cached because of which changes are not reflecting on front end immedately.

@kaalbhairava commented on GitHub (May 12, 2021): Apology for not providing the exact details. Following are the steps I performed from Netbox Administration Page: 1. Created a user named ```TestUser1``` 2. Created two permissions- **_ReadOnly - only view action is enabled for all objects ReadWrite - view, add, change, delete actions are enabled for all objects_** 3. **_ReadWrite_** permission is given to ```TestUser1``` after creation. 4. After logging in as ```TestUser1``` in Netbox , the given permission is getting reflected and I can perform view, add, change, delete actions 5. Now, I went to Administration console and changed the permission of ```TestUser1``` to _**ReadOnly**_ 6. Now, I again logged in as ```TestUser1```, but I could still add IPAddresses and prefixes. After 20-30 mins the permission changes were reflected on the front end and now I could only view. 7. After troubleshooting further, I found that the permission changes are getting reflected in database **immediately** (verified by querying the tables ), but not on the front end >** suspecting that somewhere something is getting cached because of which changes are not reflecting on front end immedately.
adam commented 2025-12-29 19:21:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 1, 2021):

Marking this as blocked by #6639 as it's believed to be a caching bug.

@jeremystretch commented on GitHub (Jul 1, 2021): Marking this as blocked by #6639 as it's believed to be a caching bug.
adam commented 2025-12-29 19:22:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 8, 2021):

This will be fixed in v3.0 with the removal of queryset caching. The workaround in the interim is to set CACHE_TIMEOUT = 0 in configuration.py.

@jeremystretch commented on GitHub (Jul 8, 2021): This will be fixed in v3.0 with the removal of queryset caching. The workaround in the interim is to set `CACHE_TIMEOUT = 0` in `configuration.py`.
adam commented 2025-12-29 19:22:05 +01:00
Author
Owner
Copy Link

@fabricat commented on GitHub (Jul 29, 2021):

This should be already fixed v2.11.10, see #6781

@fabricat commented on GitHub (Jul 29, 2021): This should be already fixed v2.11.10, see #6781
adam commented 2025-12-29 19:22:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

Note that #6781 just disables caching by default where CACHE_TIMEOUT is not set in configuration.py. If it's already been set on an existing installation, the change will have no effect: It still needs to be modified manually.

@jeremystretch commented on GitHub (Jul 29, 2021): Note that #6781 just disables caching by default where `CACHE_TIMEOUT` is not set in `configuration.py`. If it's already been set on an existing installation, the change will have no effect: It still needs to be modified manually.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4904
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?