Allow mapping Netbox groups to AD groups when using Okta #6918

Closed
opened 2025-12-29 19:46:40 +01:00 by adam · 2 comments
Owner

Originally created by @TnTBass on GitHub (Aug 31, 2022).

NetBox version

v3.2.9

Feature type

New functionality

Proposed functionality

I would like to be able to map AD groups to Netbox groups when using Okta as an SSO provider.

Use case

This would allow easy provisioning for adding or removing people to different Netbox groups. Eg: Maybe you want all people to be in a self created "Netbox ReadOnly" group, but others to have full "Netbox Admins" abilities.

When adding a new user, you could simply add them to the appropriate AD group, which Netbox would understand and map their user account to.

This is currently available with direct LDAP integration.

This either doesn't exist currently, or is unclear on how to handle this setup when using Okta.

Database changes

No response

External dependencies

No response

Originally created by @TnTBass on GitHub (Aug 31, 2022). ### NetBox version v3.2.9 ### Feature type New functionality ### Proposed functionality I would like to be able to map AD groups to Netbox groups when using Okta as an SSO provider. ### Use case This would allow easy provisioning for adding or removing people to different Netbox groups. Eg: Maybe you want all people to be in a self created "Netbox ReadOnly" group, but others to have full "Netbox Admins" abilities. When adding a new user, you could simply add them to the appropriate AD group, which Netbox would understand and map their user account to. This is currently available with direct LDAP integration. This either doesn't exist currently, or is unclear on how to handle this setup when using Okta. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:46:40 +01:00
adam closed this issue 2025-12-29 19:46:41 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 31, 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 (Oct 31, 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).
Author
Owner

@github-actions[bot] commented on GitHub (Dec 1, 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 1, 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6918