You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The heavy browser restrictions imposed upon cookies, especially in third-party contexts bring many challenges. These are discussed with details here #10979.
However, there can be valid use cases that require access to cookies in 3rd party contexts such as some identity flows. The recommendation from Safari for these scenarios is to use the storage access API and request access to cookies in 3rd party contexts.
Describe the solution you would prefer
Explore storage access API and see how Identity server flows can benefit from it. At first, the use cases with storage access API should be understood and then need to check how to leverage it for impacted Identity Server flows.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The heavy browser restrictions imposed upon cookies, especially in third-party contexts bring many challenges. These are discussed with details here #10979.
However, there can be valid use cases that require access to cookies in 3rd party contexts such as some identity flows. The recommendation from Safari for these scenarios is to use the storage access API and request access to cookies in 3rd party contexts.
In the Identity server, there are many flows impacted by the heavy cookie restrictions in 3rd party contexts. More information is described in https://wso2.com/blogs/thesource/the-impact-of-blocked-third-party-cookies-on-wso2-identity-server/.
Describe the solution you would prefer
Explore storage access API and see how Identity server flows can benefit from it. At first, the use cases with storage access API should be understood and then need to check how to leverage it for impacted Identity Server flows.
The text was updated successfully, but these errors were encountered: