SeleSign out everywhere: how SeleID revokes sessions across the apps
What happens to your sessions in SeleVista and SeleVerse when your SeleID session is revoked.
Published by SeleTech
Short answer
When a SeleID session is revoked, SeleVista and SeleVerse stop accepting it, so a lost or signed-out device no longer has access. Each session carries a generation, and revoking raises it; anything carrying an older generation is treated as signed out.
Apps check this when they start and before sensitive requests. If the check cannot be completed because of a poor connection, ordinary browsing keeps working while sensitive actions wait, so a flaky network does not lock people out unnecessarily. When a session is confirmed revoked, the app clears its tokens and sends you to sign in again.
This applies to the Sele apps. Outside apps will use the same signals when Continue with SeleID opens.
Frequently asked questions
Does revoking a session sign me out of both apps?
Yes. Both apps rely on the same SeleID session, so a revoked session stops working in both.
What if I have no signal?
Ordinary browsing can continue; sensitive actions wait until the session can be checked.
Does this apply to outside apps?
Outside apps will use the same signals when Continue with SeleID opens.