Cookie “KEYCLOAK_3P_COOKIE” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read Set-Cookie - HTTP | MDN
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
SameSite Cookie Attribute | 4 | 14806 | November 19, 2019 | |
In Keycloak 25, my cookies are showing a SameSite attribute value of "None" or blank instead of "Lax" or "Strict"; how can I configure this? | 2 | 511 | November 27, 2024 | |
How to change from SameSite=none to SameSite=Lax in KEYCLOAK_SESSION cookie? | 3 | 4746 | June 18, 2024 | |
Keycloak 9.0.0 - Cookies are not being sent with SameSite=None by the server | 5 | 9086 | August 10, 2020 | |
Keycloak support for older browsers/WebViiew | 1 | 29 | March 27, 2025 |