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

Unable to get session key working in Firefox version above 69.0.0 #2913

New Issue
Closed
opened 2025-12-29 18:23:21 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:23:21 +01:00
Owner
Copy Link

Originally created by @33Fraise33 on GitHub (Sep 26, 2019).

Environment

  • NetBox version: 2.6.1

Steps to Reproduce

  1. Download latest firefox
  2. Try to unlock a secret with a correct session key.
  3. No popup or confirmation happens, in network debugger I get 400 bad request, invalid private key
  4. This key does work on Google Chrome (with exactly the same copy paste)

Expected Behavior

Api call is done correct and key is unlocked.

Observed Behavior

400 bad request in network debugger

Comments

I'm unsure if I need to report this with Firefox or if this is something that can be fixed from netbox side.

Originally created by @33Fraise33 on GitHub (Sep 26, 2019). ### Environment * NetBox version: 2.6.1 ### Steps to Reproduce 1. Download latest firefox 2. Try to unlock a secret with a correct session key. 3. No popup or confirmation happens, in network debugger I get 400 bad request, invalid private key 4. This key does work on Google Chrome (with exactly the same copy paste) ### Expected Behavior Api call is done correct and key is unlocked. ### Observed Behavior 400 bad request in network debugger ### Comments I'm unsure if I need to report this with Firefox or if this is something that can be fixed from netbox side.
adam closed this issue 2025-12-29 18:23:21 +01:00
adam commented 2025-12-29 18:23:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2019):

NetBox version: 2.6.1

Please try upgrading to the current stable release (v2.6.5) and seeing if this problem persists. If so, please ask to re-open this issue.

@jeremystretch commented on GitHub (Sep 26, 2019): > NetBox version: 2.6.1 Please try upgrading to the current stable release (v2.6.5) and seeing if this problem persists. If so, please ask to re-open this issue.
adam commented 2025-12-29 18:23:21 +01:00
Author
Owner
Copy Link

@CosmoMyzrailGorynych commented on GitHub (Nov 14, 2019):

Please try upgrading to the current stable release (v2.6.5) and seeing if this problem persists. If so, please ask to re-open this issue.

Reopen, then.

v2.6.6
Firefox Dev edition v71.0b9 and Chromium 78.0.3904.87
My key is unlocked by admin, I have admin rights, privkey is valid. The admin user can create and read secrets, I cannot.

Edit: My problem was in using ssh-rsa keys and not rsa ones

@CosmoMyzrailGorynych commented on GitHub (Nov 14, 2019): > Please try upgrading to the current stable release (v2.6.5) and seeing if this problem persists. If so, please ask to re-open this issue. ~~Reopen, then.~~ v2.6.6 Firefox Dev edition v71.0b9 **and** Chromium 78.0.3904.87 My key is unlocked by admin, I have admin rights, privkey is valid. The `admin` user can create and read secrets, I cannot. --- **Edit:** My problem was in using ssh-rsa keys and not rsa ones
adam commented 2025-12-29 18:23:22 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 5, 2019):

I tried this on v2.6.6 with firefox 72.0b2.

  • registered a rsa public key in my account kobayashi.
  • activated it by admin
  • registered a device secret (session key was generated at this operation.)

This worked to me.
Could you try again with non openssh format?

@kobayashi commented on GitHub (Dec 5, 2019): I tried this on v2.6.6 with firefox 72.0b2. - registered a rsa public key in my account `kobayashi`. - activated it by admin - registered a device secret (session key was generated at this operation.) This worked to me. Could you try again with non openssh format?
adam commented 2025-12-29 18:23:22 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 6, 2019):

@CosmoMyzrailGorynych Please try general rsa key and If you have the same issue, open new issue because the original issue is not reproduced.

@kobayashi commented on GitHub (Dec 6, 2019): @CosmoMyzrailGorynych Please try general rsa key and If you have the same issue, open new issue because the original issue is not reproduced.
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#2913
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?