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

Secrets in Chrome based browsers. "Invalid Session Key" after undetermined period of time. #1051

New Issue
Closed
opened 2025-12-29 16:28:19 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:28:19 +01:00
Owner
Copy Link

Originally created by @phobiadhs on GitHub (Jun 22, 2017).

Note: Currently testing in Firefox as well. No indication of the issue so far.

Currently using 2.0.6.

After an undetermined period of time, when trying to unlock secrets in Chrome based browsers (Chrome and Vivaldi), a popup saying "Invalid Session Key" comes up. There is no option like normal to reenter your private key and logging out and back into Netbox has no effect. Closing and opening the browser also seems to have no effect.

Resolution seems to be to clear browser cache/cookies and log into Netbox again. Then it will work for a time.

Originally created by @phobiadhs on GitHub (Jun 22, 2017). Note: Currently testing in Firefox as well. No indication of the issue so far. Currently using 2.0.6. After an undetermined period of time, when trying to unlock secrets in Chrome based browsers (Chrome and Vivaldi), a popup saying "Invalid Session Key" comes up. There is no option like normal to reenter your private key and logging out and back into Netbox has no effect. Closing and opening the browser also seems to have no effect. Resolution seems to be to clear browser cache/cookies and log into Netbox again. Then it will work for a time.
adam closed this issue 2025-12-29 16:28:19 +01:00
adam commented 2025-12-29 16:28:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2017):

When you unlock your user key, NetBox sends a cookie named session_key to the browser, which should last for the duration of the browser session.

When you receive the "Invalid session key" error, can you check whether the session_key cookie is still present and if it has a value? It seems like maybe an empty session key is being sent. (If the cookie is missing, NetBox should prompt you to unlock your user key again.)

@jeremystretch commented on GitHub (Jun 23, 2017): When you unlock your user key, NetBox sends a cookie named `session_key` to the browser, which should last for the duration of the browser session. When you receive the "Invalid session key" error, can you check whether the `session_key` cookie is still present and if it has a value? It seems like maybe an empty session key is being sent. (If the cookie is missing, NetBox should prompt you to unlock your user key again.)
adam commented 2025-12-29 16:28:20 +01:00
Author
Owner
Copy Link

@phobiadhs commented on GitHub (Jun 23, 2017):

The cookie is there and has a value. As you said, deleting that particular cookie did kick off the user key prompt again. Trying to get it to break again so I can give you a bit more info.

@phobiadhs commented on GitHub (Jun 23, 2017): The cookie is there and has a value. As you said, deleting that particular cookie did kick off the user key prompt again. Trying to get it to break again so I can give you a bit more info.
adam commented 2025-12-29 16:28:20 +01:00
Author
Owner
Copy Link

@phobiadhs commented on GitHub (Jun 29, 2017):

I have gotten it to fail again. It took several restarts of chrome to get it to die again but it did. With that being said, I don't see any commonality between the issue and my actions.
Without being able to lock it down to specific actions, I am thinking we should probably table this unless it becomes a larger issue.

@phobiadhs commented on GitHub (Jun 29, 2017): I have gotten it to fail again. It took several restarts of chrome to get it to die again but it did. With that being said, I don't see any commonality between the issue and my actions. Without being able to lock it down to specific actions, I am thinking we should probably table this unless it becomes a larger issue.
adam commented 2025-12-29 16:28:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 2, 2017):

Closing this out since there hasn't been any further activity.

@jeremystretch commented on GitHub (Aug 2, 2017): Closing this out since there hasn't been any further activity.
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
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#1051
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?