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

add REMOTE_AUTH_EMAIL_HEADER and REMOTE_AUTH_NAME_HEADER #7626

New Issue
Closed
opened 2025-12-29 20:26:12 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:26:12 +01:00
Owner
Copy Link

Originally created by @davama on GitHub (Feb 8, 2023).

NetBox version

v3.4.4

Feature type

Change to existing functionality

Proposed functionality

There has been some great work on the REMOTE_AUTH portion, thank you for this!!

My request:

Map the REMOTE_AUTH_EMAIL_HEADER header to the email field in an account's profile.
Same with REMOTE_AUTH_NAME_HEADER header, map it to the First/Last name of the account's profile

Use case

The account data for any particular profile would be now complete with all their respective fields filled. This is mostly cosmetic.

Database changes

n/a

External dependencies

n/a

Thank you,
Dave

Originally created by @davama on GitHub (Feb 8, 2023). ### NetBox version v3.4.4 ### Feature type Change to existing functionality ### Proposed functionality There has been some great work on the REMOTE_AUTH portion, thank you for this!! My request: Map the `REMOTE_AUTH_EMAIL_HEADER` header to the email field in an account's profile. Same with `REMOTE_AUTH_NAME_HEADER` header, map it to the First/Last name of the account's profile ### Use case The account data for any particular profile would be now complete with all their respective fields filled. This is mostly cosmetic. ### Database changes n/a ### External dependencies n/a Thank you, Dave
adam added the type: featurestatus: duplicate labels 2025-12-29 20:26:12 +01:00
adam closed this issue 2025-12-29 20:26:12 +01:00
adam commented 2025-12-29 20:26:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2023):

This looks like it was implemented in NetBox v3.4.9 under #12226. Not sure why that FR was never identified as overlapping with this one.

@jeremystretch commented on GitHub (May 3, 2023): This looks like it was implemented in NetBox v3.4.9 under #12226. Not sure why that FR was never identified as overlapping with this one.
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 status: duplicate 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#7626
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?