KC-1072: action-report lock dates, compliance pw aging, security-audit record details #1759
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Three reporting enhancements for compliance and security auditing:
1. Action Report: Lock Date for Blocked Users (
aram.py)lock_timecolumn showing when users were locked--target lockedor explicit--columns lock_timelock_useraudit events to find most recent lock timestamp2. Record Access Report: Last Password Change (
compliance.py)last_pw_changecolumn in--agingreportsrecord_password_changeaudit events3. Security Audit: Per-Record Password Strength (
security_audit.py)--record-detailsflag outputs per-record password strengthget_incremental_security_dataendpoint (hasrecordUid, unlike summary endpoint)Other Changes
time_tlimits)os.killbehaviorTest Plan
Note: Full integration tests require
tests/enterprise.jsonandtests/vault.json🤖 Generated with Claude Code