Description
Google chrome changed the default behavior of SameSite parameter in Set-Cookie header from None to Lax. This causes partial breakage of Knox SSO.
Details about Chrome browser feature - https://www.chromestatus.com/feature/5088147346030592
How it affects - https://support.okta.com/help/s/article/FAQ-How-Chrome-80-Update-for-SameSite-by-default-Potentially-Impacts-Your-Okta-Environment
Attachments
Issue Links
- is related to
-
KNOX-2393 Add a configurable list of paths that SSOCookieProvider can ignore
-
- Resolved
-
- links to
