Fortinet not playing well with Supabase oauth.

# Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: - Docs: https://docs.supabase.com - Discussions: https://github.com/supabase/supabase/discussions - Discord: https://discord.supabase.com Before opening a bug report, please verify the following: --> - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). Describe the bug When using Supabase Auth on a network protected by Fortinet (e.g., FortiGate, FortiProxy), authentication flows fail due to SSL certificate errors or blocked requests. Chrome displays ERR_CERT_AUTHORITY_INVALID, preventing the auth process from completing. This is likely due to Fortinet interfering with redirects, cookies, or certificate verification. To Reproduce Steps to reproduce the behavior: Deploy a Supabase-auth-enabled application with vercel Access the application from a network using Fortinet security solutions Initiate an authentication flow Observe a browser error like ERR_CERT_AUTHORITY_INVALID or blocked redirects Expected behavior The authentication flow should complete successfully without browser security warnings or blocked network activity. Screenshots  System information OS: Windows Browser: Chrome (latest) Version of @supabase/supabase-js: e.g., 2.39.5 Version of Node.js: e.g., 18.16.0 Additional context all domains and ssl certificates are accurate, internet connection is good. website domain: https://www.adorahq.ai/ Re-signing SSL certificates with untrusted root CAs Flagging redirect/cookie patterns typical in modern auth flows This is not an issue with Supabase itself but may require documentation or guidance for users encountering…