Inventory: User Account Auto Lock
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
## User Story
In order to validate who should maintain access and who should lose access in inventory, our ISSO wants Data.gov to lock out any user that has not logged in for x days. Note: Please confirm what x days is.. 90? @sanason has managed a similar rule in Touchpoints.
## Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]
- [x] GIVEN a user has not logged in for x days \
WHEN x days + 1 occurs happens \
THEN the user account should be locked \
the user will have to request their account be unlocked.
## Background
This is predicated by our ability to unlock and lock user accounts (see ticket to be created)
## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))
[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
PLEASE CONSULT WITH @sanason and @jpyuda for security implications and create tickets as necessary to compensate.
Contributor guide
Assessment
This issue has not been assessed yet.