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

Add access restrictions for "Rendered Context". #8509

New Issue
Closed
opened 2025-12-29 20:37:36 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:37:36 +01:00
Owner
Copy Link

Originally created by @penM000 on GitHub (Aug 24, 2023).

NetBox version

v3.5.5

Feature type

New functionality

Proposed functionality

Currently, access to Source Contexts can be restricted by extras.view_configcontext, but access to Rendered Contexts cannot.

As shown in the screenshot, a user without extras.view_configcontext privileges can indirectly view Source Contexts partially through Rendered Contexts.

image
I am therefore requesting a new ? .view_renderedcontext permission and request a new feature to control access to Rendered Contexts.
? because I am not sure which affiliation is more appropriate, DCIM or extras.

Use case

This feature allows netbox users to restrict who can see the Rendered Context.
Until now, due to a bug (https://github.com/netbox-community/netbox/issues/13543),
The config context of a tab in the device view was hidden by the permission control in extras.view_configcontext, but will now be visible.
This corrective behavior provides the correct access control functionality for users who have been using this as their access control.
By controlling Rendered Contexts, we protect information from users who do not want to see the contents of Source Contexts.

Database changes

No response

External dependencies

No response

Originally created by @penM000 on GitHub (Aug 24, 2023). ### NetBox version v3.5.5 ### Feature type New functionality ### Proposed functionality Currently, access to `Source Contexts` can be restricted by `extras.view_configcontext`, but access to `Rendered Contexts` cannot. As shown in the screenshot, a user without `extras.view_configcontext` privileges can indirectly view `Source Contexts` partially through `Rendered Contexts`. ![image](https://user-images.githubusercontent.com/33054826/262965317-cb9702f3-669a-40ef-a9ef-b5de941cd3ed.png) I am therefore requesting a new `? .view_renderedcontext` permission and request a new feature to control access to `Rendered Contexts`. ? because I am not sure which affiliation is more appropriate, `DCIM` or `extras`. ### Use case This feature allows netbox users to restrict who can see the `Rendered Context`. Until now, due to a bug (https://github.com/netbox-community/netbox/issues/13543), The `config context` of a tab in the device view was hidden by the permission control in `extras.view_configcontext`, but will now be visible. This corrective behavior provides the correct access control functionality for users who have been using this as their access control. By controlling `Rendered Contexts`, we protect information from users who do not want to see the contents of `Source Contexts`. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:37:36 +01:00
adam closed this issue 2025-12-29 20:37:36 +01:00
adam commented 2025-12-29 20:37:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 23, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 23, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:37:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 23, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Dec 23, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#8509
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?