Set a time frame where users can be deactivated due to inactivity

Implementing an inactivity-based deactivation policy in Zebra involves leveraging Zebra's event listeners, scheduled tasks, or external scripts to monitor user activity and deactivate users after a specified period of inactivity. While Zebra does not provide out-of-the-box functionality specifically for deactivating users based on inactivity, its extensible platform supports custom implementations to achieve this requirement.

Functional Capabilities

  • User Login Events: Zebra records user login events, which can be used to track user activity. Custom event listeners can be developed to update a custom user attribute (e.g., lastActiveDate) each time a user logs in.

  • Scheduled Jobs for Inactivity Checks: A scheduled job or script, which can be implemented within Zebra or as an external service, periodically checks the lastActiveDate of each user. If the time since the lastActiveDate exceeds the specified inactivity period (e.g., 6 months), the script deactivates the user account.

  • Zebra Workflows for Automation: Utilise Zebra Workflows to automate user deactivation based on inactivity: Trigger: Set the workflow to trigger based on a scheduled interval (e.g., daily). User Last Login Check: Within the workflow, access user data (including last login) from Zebra. Inactivity Threshold Definition: Define an inactivity threshold (e.g., 6 months since last login). Action: Deactivate users in Zebra who haven't logged in within the threshold.

Implementation Steps for Xaana

  • Implement Custom Event Listener: Develop and deploy a custom event listener in Zebra that updates the lastActiveDate user attribute upon each user login event.

  • Create a Scheduled Job or Script: Develop a scheduled job or script that runs at regular intervals (e.g., daily) to check each user's lastActiveDate against the current date.

  • Notify Users Prior to Deactivation: Incorporate a notification system within the scheduled job or script to alert users (via email or other means) that their account is at risk of being deactivated due to inactivity.

  • Logging and Auditing: Ensure that actions taken by the scheduled job, especially deactivating users, are logged for auditing purposes. Consider creating reports or dashboards to monitor the rate and reasons for user deactivations in Zebra.

Xaana’s Differentiation - Best Practices

  • Test Thoroughly: Before deploying the custom event listener and scheduled job in production, Xaana will conduct thorough testing to ensure they work as expected without causing performance issues in Zebra.

  • Regular Review of Inactivity Threshold: Xaana recommends periodically reviewing and adjusting the inactivity threshold to align with operational needs and security policies, taking into account user feedback and usage patterns.

Last updated