Concurrent Sessions
Use the same logiccloud account from more than one place at once — for example a desktop browser and a laptop, or two tabs in different browsers — and understand how those independent sessions behave.
Before you start
Section titled “Before you start”- Prerequisites: One account, two independent browser sessions, and the portal URL.
- Required role/permission: None beyond normal sign-in. Both sessions carry the same role and therefore the same permissions.
- Settings that affect behavior:
- Max concurrent sessions (Keycloak realm/client) — some realms cap the number of simultaneous sessions per user; exceeding it can evict the oldest session.
- Single sign-out — signing out in one session may or may not end the others depending on the realm’s logout configuration.
- Editing the same resource — concurrent sessions do not lock projects; two sessions editing the same project (IDE/HMI) can overwrite each other. Coordinate edits, or treat the second session as read-only.
- Sign in to the portal in the first browser session and open your work (for example a project in the IDE).
- In a second, independent browser session, sign in with the same account. Both sessions are now active in parallel.
- Navigate and read in both — overview, devices, licensing all reflect the same organization data.
- Be careful editing the same resource from both sessions at once: changes are not merged. Save deliberately from a single session to avoid losing work.
- Sign out (or let a session expire) independently per session — see Sign out and Session refresh.
No captured steps yet. Run make regenerate-flows after a portal-e2e:docflow pipeline run produces docflow-output/concurrent-sessions.json.