Cookie Based Authentication problem

Is there a particular reason the response cookie “_sm__fch” from Zscaler Authentication server did not update to set “SameSite=None;Secure;” similar to the “_sm_au_c” Request cookie setting.

We’re currently running into a problematic scenario where the “_sm__fch” is blocked by browsers when the main site itself does not require authentication but the underlying sub-resources does require Zscaler authentication.