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

Remote Auth - Name + Email fields missing #6067

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

Originally created by @ITJamie on GitHub (Feb 9, 2022).

NetBox version

v3.1.7

Feature type

Change to existing functionality

Proposed functionality

Currently the First Name Last Name and Email fields are not populated in remote auth created users.
It would be nice to have user data fully fleshed out

There does not currently appear to be options for this.
My remote auth system can supply these as headers (well, technically i can supply Display Name (firstname and lastname combined).

Use case

Having all fields filled out in internal db for users

Database changes

No response

External dependencies

additional remote auth headers

Originally created by @ITJamie on GitHub (Feb 9, 2022). ### NetBox version v3.1.7 ### Feature type Change to existing functionality ### Proposed functionality Currently the `First Name` `Last Name` and `Email` fields are not populated in remote auth created users. It would be nice to have user data fully fleshed out There does not currently appear to be options for this. My remote auth system can supply these as headers (well, technically i can supply `Display Name` (firstname and lastname combined). ### Use case Having all fields filled out in internal db for users ### Database changes _No response_ ### External dependencies additional remote auth headers
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:36:18 +01:00
adam closed this issue 2025-12-29 19:36:19 +01:00
adam commented 2025-12-29 19:36:19 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Apr 28, 2022):

This works for me using remote auth ldap. Is this more of a social auth issue?

@ryanmerolle commented on GitHub (Apr 28, 2022): This works for me using remote auth ldap. Is this more of a social auth issue?
adam commented 2025-12-29 19:36:20 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (May 8, 2022):

No: this is about using netbox.authentication.RemoteUserBackend with data in HTTP headers, when using REMOTE_AUTH_AUTO_CREATE_USER.

The frontend proxy can supply the information in headers like OIDC_CLAIM_email, OIDC_CLAIM_given_name and OIDC_CLAIM_family_name; but there's currently no way to get Netbox pick these up into the created user, in a way corresponding to REMOTE_AUTH_GROUP_SYNC_ENABLED and REMOTE_AUTH_GROUP_HEADER.

I think this would need at least 4 new settings, such as:

REMOTE_AUTH_USER_DATA_SYNC_ENABLED
REMOTE_AUTH_USER_EMAIL_HEADER
REMOTE_AUTH_USER_FIRSTNAME_HEADER
REMOTE_AUTH_USER_LASTNAME_HEADER

To meet the original OP's requirement, they also want to accept a combined name header and split it into first name and last name algorithmically. Personally I think that logic belongs in the proxy, if it can be done there.

@candlerb commented on GitHub (May 8, 2022): No: this is about using `netbox.authentication.RemoteUserBackend` with data in HTTP headers, when using `REMOTE_AUTH_AUTO_CREATE_USER`. The frontend proxy can supply the information in headers like `OIDC_CLAIM_email`, `OIDC_CLAIM_given_name` and `OIDC_CLAIM_family_name`; but there's currently no way to get Netbox pick these up into the created user, in a way corresponding to `REMOTE_AUTH_GROUP_SYNC_ENABLED` and `REMOTE_AUTH_GROUP_HEADER`. I think this would need at least 4 new settings, such as: ``` REMOTE_AUTH_USER_DATA_SYNC_ENABLED REMOTE_AUTH_USER_EMAIL_HEADER REMOTE_AUTH_USER_FIRSTNAME_HEADER REMOTE_AUTH_USER_LASTNAME_HEADER ``` To meet the original OP's requirement, they also want to accept a combined name header and split it into first name and last name algorithmically. Personally I think that logic belongs in the proxy, if it can be done there.
adam commented 2025-12-29 19:36:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 8, 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 (Jul 8, 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).
adam commented 2025-12-29 19:36:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 8, 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 (Aug 8, 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.
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: feature
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#6067
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?