Local user switching to non-active on GET request #5351

Closed
opened 2025-12-29 19:26:58 +01:00 by adam · 0 comments
Owner

Originally created by @mmarcoux09 on GitHub (Sep 9, 2021).

NetBox version

v2.11.12-ldap

Python version

3.8

Steps to Reproduce

  1. Create local user
  2. Make the user Active
  3. Create API Token
  4. Make a API Call like -> curl -H "Authorization: Token $NETBOX_TOKEN" -k -X GET https://NETBOX.DOMAIN.COM/api/ipam/prefixes/?role=az_mgmt_subnet | jq '.results[] | .prefix'
  5. See that the user is switching to non-active and results in 403.

Expected Behavior

Once a user is active (even if a local user on a LDAP instance) it should remain active when doing a call with its token.

Observed Behavior

[09/Sep/2021:18:44:45 +0000] "GET /api/ipam/prefixes/?role=az_mgmt_subnet HTTP/1.1" 403 63 "-" "curl/7.68.0"

Originally created by @mmarcoux09 on GitHub (Sep 9, 2021). ### NetBox version v2.11.12-ldap ### Python version 3.8 ### Steps to Reproduce 1. Create local user 2. Make the user Active 3. Create API Token 4. Make a API Call like -> curl -H "Authorization: Token $NETBOX_TOKEN" -k -X GET https://NETBOX.DOMAIN.COM/api/ipam/prefixes/?role=az_mgmt_subnet | jq '.results[] | .prefix' 5. See that the user is switching to non-active and results in 403. ### Expected Behavior Once a user is active (even if a local user on a LDAP instance) it should remain active when doing a call with its token. ### Observed Behavior [09/Sep/2021:18:44:45 +0000] "GET /api/ipam/prefixes/?role=az_mgmt_subnet HTTP/1.1" 403 63 "-" "curl/7.68.0"
adam added the type: bug label 2025-12-29 19:26:58 +01:00
adam closed this issue 2025-12-29 19:26:58 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5351