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 last password change field in to user table #9618

New Issue
Closed
opened 2025-12-29 21:19:47 +01:00 by adam · 6 comments
adam commented 2025-12-29 21:19:47 +01:00
Owner
Copy Link

Originally created by @partyzan543 on GitHub (May 8, 2024).

NetBox version

3.7.5

Feature type

Data model extension

Proposed functionality

Changing the password at a certain time interval. Once every three months, or once a year. Notification of password change will be sent by email 3 or 7 days in advance

Use case

I would like to have data in the table about the last password change for the user

Database changes

add new column in to auth_user table

External dependencies

No response

Originally created by @partyzan543 on GitHub (May 8, 2024). ### NetBox version 3.7.5 ### Feature type Data model extension ### Proposed functionality Changing the password at a certain time interval. Once every three months, or once a year. Notification of password change will be sent by email 3 or 7 days in advance ### Use case I would like to have data in the table about the last password change for the user ### Database changes add new column in to auth_user table ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:19:47 +01:00
adam closed this issue 2025-12-29 21:19:47 +01:00
adam commented 2025-12-29 21:19:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 8, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 8, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:19:48 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 17, 2024):

@partyzan543 the basic idea you describe is a good one, but we need much more detail in the description if we're to move your FR forward and break it down for implementation. For example, do you imagine the change interval to be fixed or configurable per user / group / other attribute? How about the notification lead times? How configurable would the From: address on the notification emails need to be? What about media other than email for change notifications? I think you can see how quickly this request balloons if we don't set a very specific scope, and it's easy to imagine that a too-tight scope will fail to appeal to large enough portion of the user population to make it worth doing.

As an alternative, have you considered externalizing your NetBox authentication to a service that provides all these nice password aging controls? That seems to be a popular pattern.

@jeffgdotorg commented on GitHub (May 17, 2024): @partyzan543 the basic idea you describe is a good one, but we need much more detail in the description if we're to move your FR forward and break it down for implementation. For example, do you imagine the change interval to be fixed or configurable per user / group / other attribute? How about the notification lead times? How configurable would the From: address on the notification emails need to be? What about media other than email for change notifications? I think you can see how quickly this request balloons if we don't set a very specific scope, and it's easy to imagine that a too-tight scope will fail to appeal to large enough portion of the user population to make it worth doing. As an alternative, have you considered externalizing your NetBox authentication to a service that provides all these nice password aging controls? That seems to be a popular pattern.
adam commented 2025-12-29 21:19:48 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 2024):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (May 25, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:19:49 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 30, 2024):

@partyzan543 any thoughts on detailing out the description or externalizing your authentication?

@jeffgdotorg commented on GitHub (May 30, 2024): @partyzan543 any thoughts on detailing out the description or externalizing your authentication?
adam commented 2025-12-29 21:19:49 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jun 18, 2024):

@partyzan543 there's about a week left to provide the requested feedback. If we don't hear more, we'll assume you found a different way to achieve your goals.

@jeffgdotorg commented on GitHub (Jun 18, 2024): @partyzan543 there's about a week left to provide the requested feedback. If we don't hear more, we'll assume you found a different way to achieve your goals.
adam commented 2025-12-29 21:19:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 2, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Jul 2, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed 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#9618
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?