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

Azure SSO not working in maintenance mode / HA setup with Postgres in read-only mode #9493

New Issue
Closed
opened 2025-12-29 20:50:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:50:38 +01:00
Owner
Copy Link

Originally created by @bsmout on GitHub (Apr 17, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.5

Python Version

3.11

Steps to Reproduce

Netbox Docker with Azure configure as SSO provider as documented here: https://docs.netbox.dev/en/stable/administration/authentication/microsoft-azure-ad/

SSO works fine on the primary Netbox server. When streaming Postgresql to a 2nd instance with the Postgresql in read-only mode and Netbox in maintenance mode local accounts work fine but the SSO is broken.

As soon as I put the database in R/W SSO works (with Netbox still in maintenance mode).

Expected Behavior

Be able to login with both local and SSO accounts when the DB is in Read-Only mode and Netbox in maintenance mode.

Observed Behavior

The following error is thrown:

<class 'social_core.exceptions.AuthMissingParameter'>

Missing needed parameter state

Originally created by @bsmout on GitHub (Apr 17, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.5 ### Python Version 3.11 ### Steps to Reproduce Netbox Docker with Azure configure as SSO provider as documented here: https://docs.netbox.dev/en/stable/administration/authentication/microsoft-azure-ad/ SSO works fine on the primary Netbox server. When streaming Postgresql to a 2nd instance with the Postgresql in read-only mode and Netbox in maintenance mode local accounts work fine but the SSO is broken. As soon as I put the database in R/W SSO works (with Netbox still in maintenance mode). ### Expected Behavior Be able to login with both local and SSO accounts when the DB is in Read-Only mode and Netbox in maintenance mode. ### Observed Behavior The following error is thrown: <class 'social_core.exceptions.AuthMissingParameter'> Missing needed parameter state
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:50:38 +01:00
adam closed this issue 2025-12-29 20:50:38 +01:00
adam commented 2025-12-29 20:50:39 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 19, 2024):

Thanks for reporting a problem you've encountered with NetBox.

Since our team has to be able to reproduce the problem before we'll be able to confirm this bug, and since streaming PostgreSQL can be set up in more than one way, we need more detail in the Steps to Reproduce portion of your issue body. Please edit the body and decompose that section, which is currently a summary, into detailed steps. It needs to start with a freshly installed system, and be written so that a person familiar with PostgreSQL, but not familiar with streaming replication, can follow them and arrive at the same unexpected behavior you're seeing.

@jeffgdotorg commented on GitHub (Apr 19, 2024): Thanks for reporting a problem you've encountered with NetBox. Since our team has to be able to reproduce the problem before we'll be able to confirm this bug, and since streaming PostgreSQL can be set up in more than one way, we need more detail in the *Steps to Reproduce* portion of your issue body. Please edit the body and decompose that section, which is currently a summary, into detailed steps. It needs to start with a freshly installed system, and be written so that a person familiar with PostgreSQL, but *not* familiar with streaming replication, can follow them and arrive at the same unexpected behavior you're seeing.
adam commented 2025-12-29 20:50:39 +01:00
Author
Owner
Copy Link

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

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (May 17, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 status: revisions needed type: bug
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#9493
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?