NetBox version
4.6.1
Feature type
Data model extension
Proposed functionality
Issue #20929 introduced the render_config permission to control who can render and view a device's rendered configuration. This is a great improvement for protecting sensitive configuration data.
However, the Rendered Context tab remains visible in the UI and API. Similar to the concerns described in #20929, this can expose sensitive information in environments where the rendered context contains passwords, tokens, or other secrets.
Use case
Just like the rendered configuration, the rendered context may contain sensitive values that should not be visible to users who only need access to the device inventory.
Would it be possible to either:
- Hide/disable Rendered Context when the
render_config permission is not granted; or
- Introduce a separate permission (e.g.
render_context) to control access to the rendered context independently?
Database changes
No response
External dependencies
No response
NetBox version
4.6.1
Feature type
Data model extension
Proposed functionality
Issue #20929 introduced the
render_configpermission to control who can render and view a device's rendered configuration. This is a great improvement for protecting sensitive configuration data.However, the Rendered Context tab remains visible in the UI and API. Similar to the concerns described in #20929, this can expose sensitive information in environments where the rendered context contains passwords, tokens, or other secrets.
Use case
Just like the rendered configuration, the rendered context may contain sensitive values that should not be visible to users who only need access to the device inventory.
Would it be possible to either:
render_configpermission is not granted; orrender_context) to control access to the rendered context independently?Database changes
No response
External dependencies
No response