If they’re testing on localhost , it could be (I’m assuming Chrome) defaulting to lax if the SameSite attribute is not specified. See this Chrome feature which started rolling out from July 2020. So it could be Chrome just reporting that default.
When SameSite was implemented in this SDK, we decided at the time to specify none when running on HTTPS, and not specify anything at all (inherit browser defaults) when not running on HTTPS.
For example, ‘domain name a’ and ‘domain name B’ use the same auth0 application. What will be passed in the set-cookie?
For example: token? Or what information? We need to evaluate whether the information leakage will cause harm to our customers?
You can see the contents of that cookie by inspecting the application. It contains a boolean value to indicate if the application should perform a silent auth request (just a request, not a form of authentication).