Login Insights: Successful and Failed Login Metrics

[hifabienne]

As an administrator, I want to retrieve insights about successful and failed login attempts, filtered by time range and level (instance, organization, or application), so that I can monitor login activity, identify potential security threats, and analyze user authentication patterns.

Description:

To enhance security monitoring and gain insights into user authentication patterns, administrators need access to login metrics. This feature provides data on successful and failed login attempts, allowing for filtering by time range and level (overall instance, within a specific organization, or for a particular application). This will enable administrators to detect suspicious login activity, analyze authentication trends, and proactively address potential security concerns.

Acceptance Criteria:

• Successful Login Count:
  • Given: An administrator requests login insights.
  • Then: The system should provide the count of successful login attempts.
• Failed Login Count:
  • Given: An administrator requests login insights.
  • Then: The system should provide the count of failed login attempts.
• Time Range Filtering:
  • Given: An administrator requests login insights.
  • When: The administrator specifies a start and end date for the time range.
  • Then: The returned metrics should only include login attempts within the specified time range.
• Level Filtering (Instance):
  • Given: An administrator requests login insights.
  • When: The administrator selects "instance" as the level.
  • Then: The returned metrics should include login attempts across the entire instance.
• Level Filtering (Organization):
  • Given: An administrator requests login insights.
  • When: The administrator selects a specific organization as the level.
  • Then: The returned metrics should only include login attempts within that organization.
• Level Filtering (Project):
  • Given: An administrator requests login insights.
  • When: The administrator selects a specific project as the level.
  • Then: The returned metrics should only include login attempts within that project.
• Level Filtering (Application):
  • Given: An administrator requests login insights.
  • When: The administrator selects a specific application as the level.
  • Then: The returned metrics should only include login attempts for that application.
• Data Accessibility (UI):
  • Given: An administrator accesses the management console UI.
  • Then: There should be a section or page dedicated to displaying login insights.
  • And: The metrics should be presented in a clear and understandable format.
  • And: There should be filtering capabilities for time range and level.
• Data Accessibility (API):
  • Given: An administrator requests login insights through an API.
  • Then: The system should provide an API endpoint to retrieve login insights.
  • And: The API should return data in a standard format (e.g., JSON).
  • And: The API should support filtering for time range and level.
• Performance:
  • Given: The system retrieves login insights.
  • Then: The retrieval should be performed efficiently without significant performance degradation.
• Documentation:
  • Given: An administrator or developer accesses the system documentation.
  • Then: The documentation should explain:
    • The available login insights metrics.
    • How to access the metrics through the UI and API.
    • The filtering options for time range and level.
    • The format of the data.
• Testing:
  • Given: The login insights feature is implemented.
  • Then:
    • Unit tests should verify individual metric retrieval functions.
    • Integration tests should verify the interaction between different data access components.
    • End-to-end tests should simulate user workflows, including successful and failed login attempts with different filters.
    • Test cases should cover valid and invalid filtering scenarios.

[gamefb]

Any updates on this? I would think logging login attempts would be a minimum viable product feature