Support new API_TOKEN format #1532
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tobiasge
force-pushed
the
new-api-token
branch
from
0be96d4 to
360ebc1
Compare
Allows configuration the new API_TOKEN_PEPPERS setting from an ENV variable or secret file. Feature request: netbox-community/netbox#20210 Pull request: netbox-community/netbox#20477
tobiasge
force-pushed
the
new-api-token
branch
from
360ebc1 to
1f0ef02
Compare
cimnine
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue: netbox-community/netbox#20210
New Behavior
API_TOKEN_PEPPERSsettingContrast to Current Behavior
Discussion: Benefits and Drawbacks
Changes to the Wiki
Proposed Release Note Entry
API_TOKEN_PEPPERSsettingDouble Check
developbranch.