Closed PaulBol closed 2 years ago
There are two different cookies used during the Saml2 login:
It's only the correlation cookie that is set directly by the Saml2 handler - that is the one controlled by the Saml2 EmitSameSiteNone callback. The session cookie is set by Asp.Net Core's cookie handler through the cookie manager - please consult that documentation on how to control the same site mode. And by the way, SameSite=Lax (which is the default) is both sound from a security perspective and has good compatibility across browsers. It i sonly the explicit SameSite=None that needs to be handled differently for some older browsers.
Alright, I see that I was barking up the wrong tree. Thanks for the swift clarification and sorry for my ignorance.
Setup
Behavior
samesite=none
I tried the same with
EmitSameSiteNone = (x) => false
with unchanged results.