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

Deterministically expose username of logged-in user #9990

New Issue
Closed
opened 2025-12-29 21:25:20 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:25:20 +01:00
Owner
Copy Link

Originally created by @jeffgdotorg on GitHub (Jul 17, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.0.7

Feature type

Change to existing functionality

Proposed functionality

Add an invisible DOM element, and/or inject a JS variable, that can be relied upon as a stable way to learn the username of the currently logged-in user. The item's absence, or its presence with a nullish value, indicates that no user is currently logged in. Implementation should be as independent as possible of the frontend technology stack, so that it remains useful across successive releases.

Use case

The immediate driver for this FR is an embedded help center present in some NetBox product editions. It's broadly useful enough, though, that it should be present in all instances.

Database changes

None

External dependencies

None

Originally created by @jeffgdotorg on GitHub (Jul 17, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.0.7 ### Feature type Change to existing functionality ### Proposed functionality Add an invisible DOM element, and/or inject a JS variable, that can be relied upon as a stable way to learn the username of the currently logged-in user. The item's absence, or its presence with a nullish value, indicates that no user is currently logged in. Implementation should be as independent as possible of the frontend technology stack, so that it remains useful across successive releases. ### Use case The immediate driver for this FR is an embedded help center present in some NetBox product editions. It's broadly useful enough, though, that it should be present in all instances. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:25:20 +01:00
adam closed this issue 2025-12-29 21:25:20 +01:00
adam commented 2025-12-29 21:25:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2024):

We could do this with data attributes on e.g. the root element. (We already use this approach for conveying the view's URL name and base path.)

<html data-netbox-user-name="jstretch" data-netbox-user-id="123">
@jeremystretch commented on GitHub (Jul 17, 2024): We could do this with data attributes on e.g. the root element. (We already use this approach for conveying the view's URL name and base path.) ``` <html data-netbox-user-name="jstretch" data-netbox-user-id="123"> ```
adam commented 2025-12-29 21:25:21 +01:00
Author
Owner
Copy Link

@RangerRick commented on GitHub (Jul 17, 2024):

We could do this with data attributes on e.g. the root element. (We already use this approach for conveying the view's URL name and base path.)

Ooh yeah, that would be perfect.

@RangerRick commented on GitHub (Jul 17, 2024): > We could do this with data attributes on e.g. the root element. (We already use this approach for conveying the view's URL name and base path.) Ooh yeah, that would be perfect.
adam commented 2025-12-29 21:25:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2024):

We discussed broadening the scope of this FR to also entail things like the running NetBox version and edition. I'm going to explore whether the approach above suffices or there's a more preferable convention for doing so.

@jeremystretch commented on GitHub (Jul 17, 2024): We discussed broadening the scope of this FR to also entail things like the running NetBox version and edition. I'm going to explore whether the approach above suffices or there's a more preferable convention for doing so.
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 complexity: low status: accepted 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#9990
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?