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

New LDAP Group Permissions failed #4094

New Issue
Closed
opened 2025-12-29 18:33:05 +01:00 by adam · 8 comments
adam commented 2025-12-29 18:33:05 +01:00
Owner
Copy Link

Originally created by @thoms27 on GitHub (Sep 10, 2020).

Environment

  • Python version: 3.8.2
  • NetBox version: 2.9.2

Steps to Reproduce

  1. Create a group on your AD (ex: g_netbox) and a user (ex: netbox)

  2. Under Netbox Administration, create a new group (g_netbox)

  3. Under Netbox Administration, add a permission to this group (ex: dcim.view_site):
    image

  4. Try to logging as user 'netbox'

Expected Behavior

Logging established and only view Site is possible

Observed Behavior

Logging is OK, View Site is not allowed
image

I have an old group (before the last upgrade (v2.8.0) and it's works.
To complete, if I manually attach the new user to the group in Netbox Administration, it's works :
image

and

image

With my old group, it's not necessary to manually attach user to the group.

Regards

Originally created by @thoms27 on GitHub (Sep 10, 2020). ### Environment * Python version: 3.8.2 * NetBox version: 2.9.2 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Create a group on your AD (ex: g_netbox) and a user (ex: netbox) 2. Under Netbox Administration, create a new group (g_netbox) 3. Under Netbox Administration, add a permission to this group (ex: dcim.view_site): ![image](https://user-images.githubusercontent.com/20238377/92722622-27512880-f368-11ea-9469-f7f5c3396bcf.png) 4. Try to logging as user 'netbox' ### Expected Behavior <!-- What did you expect to happen? --> Logging established and only view Site is possible ### Observed Behavior <!-- What happened instead? --> Logging is OK, View Site is not allowed ![image](https://user-images.githubusercontent.com/20238377/92722462-f2dd6c80-f367-11ea-95f2-5f9cd10f4da2.png) I have an old group (before the last upgrade (v2.8.0) and it's works. To complete, if I manually attach the new user to the group in Netbox Administration, it's works : ![image](https://user-images.githubusercontent.com/20238377/92723257-1fde4f00-f369-11ea-9bc5-b86872dea6ed.png) and ![image](https://user-images.githubusercontent.com/20238377/92723294-2b317a80-f369-11ea-9320-5c7699804030.png) With my old group, it's not necessary to manually attach user to the group. Regards
adam added the type: bugstatus: needs ownerpending closure labels 2025-12-29 18:33:05 +01:00
adam closed this issue 2025-12-29 18:33:05 +01:00
adam commented 2025-12-29 18:33:05 +01:00
Author
Owner
Copy Link

@abenedict commented on GitHub (Sep 10, 2020):

I am seeing the exact same issue.

@abenedict commented on GitHub (Sep 10, 2020): I am seeing the exact same issue.
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@crazyman143 commented on GitHub (Oct 6, 2020):

Same issue on 2.9.4.
Anyone know of a fix ?

@crazyman143 commented on GitHub (Oct 6, 2020): Same issue on 2.9.4. Anyone know of a fix ?
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@pairbear commented on GitHub (Nov 17, 2020):

Running into a similar issue in 2.9.9 as well

@pairbear commented on GitHub (Nov 17, 2020): Running into a similar issue in 2.9.9 as well
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Nov 25, 2020):

I'm running v2.9.10 and have been tinkering with this as I was initially seeing some confusing behavior.

For the most part, everything seems to be working fine with the LDAP group permissions mapping - with the exception of scripts and reports. I can't seem to get a user with View/Add/Change/Delete rights on "scripts" and "reports to be able to access or run either. Both options are greyed out in the menu.

[edit] I'm continuing to look in to this, just putting this info here as notes on my findings/observations

image
image

Edit 2:

The running reports & scripts issue was supposedly due to new "run" permissions being required, however adding "run" as described in the docs doesn't seem to be doing it.

@tyler-8 commented on GitHub (Nov 25, 2020): I'm running v2.9.10 and have been tinkering with this as I was initially seeing some confusing behavior. For the most part, everything seems to be working fine with the LDAP group permissions mapping - with the exception of scripts and reports. I can't seem to get a user with View/Add/Change/Delete rights on "scripts" and "reports to be able to access or run either. Both options are greyed out in the menu. [edit] I'm continuing to look in to this, just putting this info here as notes on my findings/observations ![image](https://user-images.githubusercontent.com/17618971/100163006-c1fad700-2e82-11eb-8cba-f74afba2008d.png) ![image](https://user-images.githubusercontent.com/17618971/100163025-ccb56c00-2e82-11eb-9f96-c3e442769f6f.png) Edit 2: The running reports & scripts issue was supposedly due to [new "run" permissions](https://netbox.readthedocs.io/en/stable/additional-features/custom-scripts/#running-custom-scripts) being required, however adding "run" as described in the docs doesn't seem to be doing it.
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 9, 2021):

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. Please see our contributing guide.

@stale[bot] commented on GitHub (Jan 9, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 24, 2021):

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.

@stale[bot] commented on GitHub (Jan 24, 2021): 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.
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@thoms27 commented on GitHub (Feb 2, 2021):

Any news ?

@thoms27 commented on GitHub (Feb 2, 2021): Any news ?
adam commented 2025-12-29 18:33:06 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Feb 3, 2021):

Try enabling group mirroring and see if that provides a workable solution. I've tried to summarize a longer thread here: https://github.com/netbox-community/netbox/issues/5442#issuecomment-770997825

@tyler-8 commented on GitHub (Feb 3, 2021): Try enabling group mirroring and see if that provides a workable solution. I've tried to summarize a longer thread here: https://github.com/netbox-community/netbox/issues/5442#issuecomment-770997825
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: 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#4094
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?