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

Add USE_X_FORWARDED_PORT to settings #6855

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

Originally created by @sol1-matt on GitHub (Aug 23, 2022).

NetBox version

v3.3.0

Feature type

New functionality

Proposed functionality

Add new setting USE_X_FORWARDED_PORT for SAML auth through a transparent proxy.

Use case

Enable SAML to work with Netbox through transparent proxy.

When django is running through a transparent proxy an error can occur because the listening port for the django app is different from the SAML return url.

Authentication failed: SAML login failed: ['invalid_response'] 
(The response was received at https://netbox.example.com:8000/social/complete/saml/ instead of https://netbox.example.com/social/complete/saml/)

The solution for any django app is to add a X-Forwarded-Port header to the proxy and set USE_X_FORWARDED_PORT = True in the django application.

An example of the problem and solution can be found here.

Database changes

none

External dependencies

none

Originally created by @sol1-matt on GitHub (Aug 23, 2022). ### NetBox version v3.3.0 ### Feature type New functionality ### Proposed functionality Add new setting `USE_X_FORWARDED_PORT` for SAML auth through a transparent proxy. ### Use case Enable SAML to work with Netbox through transparent proxy. When django is running through a transparent proxy an error can occur because the listening port for the django app is different from the SAML return url. ``` Authentication failed: SAML login failed: ['invalid_response'] (The response was received at https://netbox.example.com:8000/social/complete/saml/ instead of https://netbox.example.com/social/complete/saml/) ``` The solution for any django app is to add a `X-Forwarded-Port` header to the proxy and set `USE_X_FORWARDED_PORT = True` in the django application. An example of the problem and solution can be found [here](https://github.com/onelogin/python3-saml/issues/83). ### Database changes none ### External dependencies none
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:46:05 +01:00
adam closed this issue 2025-12-29 19:46:06 +01:00
adam commented 2025-12-29 19:46:06 +01:00
Author
Owner
Copy Link

@sol1-matt commented on GitHub (Aug 23, 2022):

The specific auth provider this was needed for is Jumpcloud with a Nginx proxy in front of uwsgi on port 8000. The proxy is on the Netbox server and the domain for Nginx and uwsgi is the same.

There is an additional setting USE_X_FORWARDED_HOST which I haven't tested but probably does what it says on the box.

@sol1-matt commented on GitHub (Aug 23, 2022): The specific auth provider this was needed for is Jumpcloud with a Nginx proxy in front of uwsgi on port 8000. The proxy is on the Netbox server and the domain for Nginx and uwsgi is the same. There is an additional setting `USE_X_FORWARDED_HOST` which I haven't tested but probably does what it says on the box.
adam commented 2025-12-29 19:46:06 +01:00
Author
Owner
Copy Link

@sol1-matt commented on GitHub (Aug 23, 2022):

tested solution here 26ee79cdf9
conjunction with USE_X_FORWARDED_HOST = True in configuration.py

@sol1-matt commented on GitHub (Aug 23, 2022): tested solution here https://github.com/sol1-matt/netbox/commit/26ee79cdf90f6c25258bece3232ff67a8502231b conjunction with `USE_X_FORWARDED_HOST = True` in `configuration.py`
adam commented 2025-12-29 19:46:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 16, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 16, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:46:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 17, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Dec 17, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner type: feature
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#6855
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?