starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Keywordlookup not working #11436

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

Originally created by @hagen-bauer-regioit on GitHub (Aug 1, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.5

Python Version

3.11

Steps to Reproduce

I am running Netbox with LDAP Authentication. When I want to create a new Device and get the Devicerole the dialogbox is empty. In the Webserver log I can see that the request is done unauthenticated

xxxx - hagen.bauer@regioit.de [01/Aug/2025:12:07:31 +0200] "GET /static/Inter-Medium-JV63DMR7.woff2?v=3.18 HTTP/1.1" 200 105616 xxxx - - [01/Aug/2025:12:08:22 +0200] "GET /api/dcim/device-types/?brief=true&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:08:51 +0200] "GET /api/dcim/device-roles/?brief=true&limit=100 HTTP/1.1" 403 33
This also applies to other diaglogboxes that should display keywords.

xxxx - - [01/Aug/2025:12:10:22 +0200] "GET /api/tenancy/tenants/?brief=true&group_id=1&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:10:26 +0200] "GET /api/tenancy/tenant-groups/?brief=true&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:10:51 +0200] "GET /api/dcim/sites/?brief=true&limit=100 HTTP/1.1" 403 33

Expected Behavior

The dialog box should display the correct values

Observed Behavior

Dialogbox is empty

Originally created by @hagen-bauer-regioit on GitHub (Aug 1, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.5 ### Python Version 3.11 ### Steps to Reproduce I am running Netbox with LDAP Authentication. When I want to create a new Device and get the Devicerole the dialogbox is empty. In the Webserver log I can see that the request is done unauthenticated `xxxx - hagen.bauer@regioit.de [01/Aug/2025:12:07:31 +0200] "GET /static/Inter-Medium-JV63DMR7.woff2?v=3.18 HTTP/1.1" 200 105616 xxxx - - [01/Aug/2025:12:08:22 +0200] "GET /api/dcim/device-types/?brief=true&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:08:51 +0200] "GET /api/dcim/device-roles/?brief=true&limit=100 HTTP/1.1" 403 33 ` This also applies to other diaglogboxes that should display keywords. ` xxxx - - [01/Aug/2025:12:10:22 +0200] "GET /api/tenancy/tenants/?brief=true&group_id=1&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:10:26 +0200] "GET /api/tenancy/tenant-groups/?brief=true&limit=100 HTTP/1.1" 403 33 xxxx - - [01/Aug/2025:12:10:51 +0200] "GET /api/dcim/sites/?brief=true&limit=100 HTTP/1.1" 403 33 ` ### Expected Behavior The dialog box should display the correct values ### Observed Behavior Dialogbox is empty
adam added the type: bug label 2025-12-29 21:45:12 +01:00
adam closed this issue 2025-12-29 21:45:12 +01:00
adam commented 2025-12-29 21:45:13 +01:00
Author
Owner
Copy Link

@hagen-bauer-regioit commented on GitHub (Aug 1, 2025):

This happens with Microsoft Edge. Firefox is working fine

@hagen-bauer-regioit commented on GitHub (Aug 1, 2025): This happens with Microsoft Edge. Firefox is working fine
adam commented 2025-12-29 21:45:14 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Aug 1, 2025):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior.

The symptoms you're describing (403 errors on API endpoints for authenticated users) suggest this may be related to your specific LDAP configuration or environment setup rather than a bug in NetBox itself. If this were a NetBox bug, we would typically expect to see similar reports from other users with LDAP configurations.

Each bug report must include detailed steps to reproduce the issue starting from a vanilla NetBox installation. However, given that reproducing this would likely require replicating your specific LDAP setup, this issue may be better suited for https://github.com/netbox-community/netbox/discussions/categories/help-wanted where the community can provide configuration and troubleshooting assistance.

The bug tracker is intended for reproducible defects in NetBox's code, not for configuration or deployment support. If you can provide detailed reproduction steps that can be followed on a standard NetBox installation, please update this issue with those details. Otherwise, we recommend seeking help through GitHub Discussions.

@jnovinger commented on GitHub (Aug 1, 2025): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. The symptoms you're describing (403 errors on API endpoints for authenticated users) suggest this may be related to your specific LDAP configuration or environment setup rather than a bug in NetBox itself. If this were a NetBox bug, we would typically expect to see similar reports from other users with LDAP configurations. Each bug report must include detailed steps to reproduce the issue starting from a vanilla NetBox installation. However, given that reproducing this would likely require replicating your specific LDAP setup, this issue may be better suited for https://github.com/netbox-community/netbox/discussions/categories/help-wanted where the community can provide configuration and troubleshooting assistance. The bug tracker is intended for reproducible defects in NetBox's code, not for configuration or deployment support. If you can provide detailed reproduction steps that can be followed on a standard NetBox installation, please update this issue with those details. Otherwise, we recommend seeking help through GitHub Discussions.
adam commented 2025-12-29 21:45:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 9, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Aug 9, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:45:14 +01:00
Author
Owner
Copy Link

@hagen-bauer-regioit commented on GitHub (Aug 13, 2025):

you can close this issue. I can work.

@hagen-bauer-regioit commented on GitHub (Aug 13, 2025): you can close this issue. I can work.
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 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#11436
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?