From 23211b178404e7da3ea0fa8bbcf4bcec205cb874 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Sat, 6 Apr 2024 03:15:21 +0200 Subject: [PATCH] clarify that session scoping is needed even when other forms of identification are used --- source/docs/v3/session-scoping.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/docs/v3/session-scoping.blade.md b/source/docs/v3/session-scoping.blade.md index e20af26..2f5f02f 100644 --- a/source/docs/v3/session-scoping.blade.md +++ b/source/docs/v3/session-scoping.blade.md @@ -8,7 +8,7 @@ section: content Session scoping is one thing that you might have to deal with yourself. -The issue occurs when you're using multiple tenant domains and databases. Users can change their session cookie's domain and their session data will be shared in another tenant's application. +The issue occurs when you're using multiple tenant databases. Users can change their session cookie's domain and their session data will be shared in another tenant's application. Here's how you can prevent this.