API Integration for Active Sessions Management

[yahyafakhroji]

Summary

Integrate backend APIs for active sessions management. Display all active sessions with device information and allow users to revoke individual sessions or terminate all other sessions. Replace dummy session data with real API calls.

Scope

1. List Active Sessions

Display Data:

• Device name (browser + OS, e.g., "Chrome on Windows 10")
• Session ID (to indicate current active session)
• Location (city, country or IP address)
• Last used (timestamp/relative time)

Features:

• Auto-refresh sessions list every 30 seconds
• Highlight current session (cannot be revoked)
• Display session status indicator (active/idle)
• Sort by last used (most recent first)

2. Revoke Individual Session

Features:

• Confirmation dialog before revoking
• Show which device will be logged out
• Immediate removal from list on success
• Cannot revoke current session
• Success notification

3. Update Docs

• Add some documentation around handling your user sessions - good example from CF here

[yahyafakhroji]

API is ready to integrate. Sample usage in Staff Portal -> My Profile

[mattdjenkinson]

@yahyafakhroji @OscarLlamas6 @JoseSzycho do you know why the created date is just the current date time?

[JoseSzycho]

@mattdjenkinson this is how a raw session looks like:

✗ kubectl --kubeconfig staffuser get sessions 354836802730724040 -o yaml

apiVersion: identity.miloapis.com/v1alpha1
kind: Session
metadata:
  creationTimestamp: null
  name: "354836802730724040"
status:
  createdAt: "2026-01-09T21:46:55Z"
  expiresAt: "2026-01-19T21:46:55Z"
  fingerprintID: 34017cf5-e0a2-44a6-b93b-da08cd06e11c
  ip: 186.158.228.76
  provider: zitadel
  userUID: "341931253005553172"

The creationTimestamp is null, as actually, the resource has never been created into the etcd, as this is a custom API.

I think that the listing method is using a default value as the creationTimestamp is null, and that default date is the current date time. The front end table should use the status.createdAt field instead.

Here's an example that shows that all of my current sessions actually have different creation date.

✗ kubectl --kubeconfig staffuser get sessions -o yaml | grep createdAt

    createdAt: "2025-11-10T15:24:48Z"
    createdAt: "2025-10-30T16:27:01Z"
    createdAt: "2025-12-05T16:01:49Z"
    createdAt: "2025-11-10T15:38:57Z"
    createdAt: "2025-10-20T12:24:27Z"
    createdAt: "2025-10-31T21:17:07Z"
    createdAt: "2025-10-30T16:36:54Z"
    createdAt: "2025-10-12T21:01:49Z"
    createdAt: "2025-10-12T21:51:04Z"
    createdAt: "2025-11-12T13:53:59Z"
    createdAt: "2025-11-12T14:26:11Z"
    createdAt: "2025-10-16T21:38:06Z"
    createdAt: "2025-11-03T18:03:43Z"
    createdAt: "2025-12-08T19:41:30Z"
    createdAt: "2025-11-12T15:40:35Z"
    createdAt: "2025-10-29T22:41:55Z"
    createdAt: "2026-01-07T14:57:21Z"
    createdAt: "2025-12-09T19:20:13Z"
    createdAt: "2025-12-08T20:09:34Z"
    createdAt: "2025-12-08T20:23:08Z"
    createdAt: "2026-01-07T15:29:14Z"
    createdAt: "2025-11-18T13:01:45Z"
    createdAt: "2025-12-30T14:10:52Z"
    createdAt: "2025-12-09T14:51:05Z"
    createdAt: "2025-11-04T12:50:01Z"
    createdAt: "2025-11-10T14:59:54Z"
    createdAt: "2026-01-07T15:48:59Z"
    createdAt: "2025-12-22T17:38:43Z"
    createdAt: "2026-01-14T14:40:06Z"
    createdAt: "2026-01-09T21:46:55Z"