Enhance SSO Workflow for Cross-Domain Authentication

Describe the Improvement Current Behavior The existing SSO flow works as follows: 1. Main application redirects to Directus login 2. Directus redirects to Google 3. Google authenticates user and redirects back to Directus 4. Directus creates/signs in user and sets browser cookie 5. Directus redirects back to main application Problem When the main application and Directus are on different domains, server-side authentication becomes problematic: The main application's server cannot access Directus authentication cookies. This makes it impossible to verify user permissions or authentication status server-side. Proposed improvement Could you add the capability for authenticated users to request a session token that can be read from the API response? This will allow browser clients to manually set the session cookie for the current domain they are visiting, allowing the server-side application to read that session and use it to authenticate and validate user p…