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.]
Background
This is predicated by our ability to unlock and lock user accounts (see ticket to be created)
Security Considerations (required)
[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.
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.]
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)
[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.