liveBook · Manning

Session isolation

As explained in Software Security for Developers

Isolated session management is the practice of maintaining authentication sessions separately so activity in one tenant does not affect another tenant's sessions.

Isolated session management keeps authentication sessions separate for each tenant. This prevents activity in one tenant from changing another tenant’s session state. section 13.4

Tenant-specific logout

A user logged into two tenant environments can log out of one tenant’s application without losing the session in the other tenant’s environment. section 13.4

How Software Security for Developers covers it

How deep it goes
Defines the isolation goal and logout behavior but does not describe implementation steps or session internals.
Examples
Uses separate tenant authentication flows and logout from one tenant’s application without affecting another tenant.
What you can do after
Evaluate/understand whether tenant logout behavior preserves session isolation across environments.
How it connects
Connects OpenID Connect with multitenancy, authentication flows, and tenant-specific authorization.
Cover of Software Security for Developers
liveBookmanning.com
Read Software Security for Developers on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Software Security for Developers. The section links point to the parts of the book it draws on.