Group checks are case-sensitive #6613

Closed
opened 2025-12-29 19:43:08 +01:00 by adam · 3 comments
Owner

Originally created by @jschewebbn on GitHub (Jun 30, 2022).

NetBox version

v3.1.7

Python version

3.8

Steps to Reproduce

Use LDAP as the group authentication provider.
I am adding permissions using the REST API.

Expected Behavior

If I enter the group name "test" into the API and LDAP returns "TEST" the permission is denied until I modify the permission to reference "TEST". The checking of groups should not be case-sensitive.

Observed Behavior

Access is denied.

Originally created by @jschewebbn on GitHub (Jun 30, 2022). ### NetBox version v3.1.7 ### Python version 3.8 ### Steps to Reproduce Use LDAP as the group authentication provider. I am adding permissions using the REST API. ### Expected Behavior If I enter the group name "test" into the API and LDAP returns "TEST" the permission is denied until I modify the permission to reference "TEST". The checking of groups should not be case-sensitive. ### Observed Behavior Access is denied.
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:43:08 +01:00
adam closed this issue 2025-12-29 19:43:08 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 1, 2022):

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. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Jul 1, 2022): 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. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
Author
Owner

@jschewebbn commented on GitHub (Jul 1, 2022):

I was hoping that someone would be able to easily say that's expected or not. I'll work on more detailed instructions.

@jschewebbn commented on GitHub (Jul 1, 2022): I was hoping that someone would be able to easily say that's expected or not. I'll work on more detailed instructions.
Author
Owner

@jeremystretch commented on GitHub (Jul 19, 2022):

Closing this out as no further detail has been provided.

@jeremystretch commented on GitHub (Jul 19, 2022): Closing this out as no further detail has been provided.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6613