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

netbox 3.6-beta1 - api tokens - keys now hidden in ui #8452

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

Originally created by @ITJamie on GitHub (Aug 10, 2023).

Originally assigned to: @jeremystretch on GitHub.

Change Type

Correction

Area

Integrations/API

Proposed Changes

I noticed in the release notes for 3.6-beta1 there is no mention of the fact that API tokens are now partially hidden in the UI for both users under "API Tokens" and in the admin section.

This is a change from past behavior where API keys were viewable, which should probably get called out in the release notes.

Originally created by @ITJamie on GitHub (Aug 10, 2023). Originally assigned to: @jeremystretch on GitHub. ### Change Type Correction ### Area Integrations/API ### Proposed Changes I noticed in the release notes for 3.6-beta1 there is no mention of the fact that API tokens are now partially hidden in the UI for both users under "API Tokens" and in the admin section. This is a change from past behavior where API keys were viewable, which should probably get called out in the release notes.
adam added the status: acceptedtype: documentationbeta labels 2025-12-29 20:36:55 +01:00
adam closed this issue 2025-12-29 20:36:56 +01:00
adam commented 2025-12-29 20:36:56 +01:00
Author
Owner
Copy Link

@tagur87 commented on GitHub (Aug 10, 2023):

They are also obfuscated in the API: https://beta-demo.netbox.dev/api/users/tokens/

Also appears that you cannot even see the full token when allowing netbox to create the token for you.

@tagur87 commented on GitHub (Aug 10, 2023): They are also obfuscated in the API: https://beta-demo.netbox.dev/api/users/tokens/ Also appears that you cannot even see the full token when allowing netbox to create the token for you.
adam commented 2025-12-29 20:36:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2023):

@tagur87 this is not related to any work done in v3.6. The ALLOW_TOKEN_RETRIEVAL configuration parameter was introduced in v3.4.0, and is currently disabled on the demo instance.

@jeremystretch commented on GitHub (Aug 10, 2023): @tagur87 this is not related to any work done in v3.6. The [`ALLOW_TOKEN_RETRIEVAL`](https://docs.netbox.dev/en/stable/configuration/security/#allow_token_retrieval) configuration parameter was introduced in v3.4.0, and is currently disabled on the demo instance.
adam commented 2025-12-29 20:36:58 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Aug 10, 2023):

apologies, closing out

@ITJamie commented on GitHub (Aug 10, 2023): apologies, closing out
adam commented 2025-12-29 20:36:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2023):

API tokens are now partially hidden in the UI for both users under "API Tokens" and in the admin section.

@ITJamie I think you're right to flag this detail. Previously, token keys were always visible in the admin UI. Now that they've been moved to the proper frontend, admins also cannot view token keys when ALLOW_TOKEN_RETRIEVAL is disabled.

@jeremystretch commented on GitHub (Aug 10, 2023): > API tokens are now partially hidden in the UI for both users under "API Tokens" and in the admin section. @ITJamie I think you're right to flag this detail. Previously, token keys were always visible in the admin UI. Now that they've been moved to the proper frontend, admins also cannot view token keys when `ALLOW_TOKEN_RETRIEVAL` is disabled.
adam commented 2025-12-29 20:36:59 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Aug 10, 2023):

No probs ether way. I was comparing against the normal demo instance so i had assumed the config settings would be the same.

Probably good that it wasnt to catch this

@ITJamie commented on GitHub (Aug 10, 2023): No probs ether way. I was comparing against the normal demo instance so i had assumed the config settings would be the same. Probably good that it wasnt to catch this
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 beta status: accepted type: documentation
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#8452
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?