Hi @Sarah
@Marilee Turscak-MSFT 's comment is correct. And I find a soultion documented by the aspnet/security team on GitHub..
You can try below methods to solve your issue.
1. If you are using ASP.NET Core Identity you disable the protection by configuring cookies with the following code
services.ConfigureExternalCookie(options => {
// Other options
options.Cookie.SameSite = SameSiteMode.None; }); services.ConfigureApplicationCookie(options => {
// Other options
options.Cookie.SameSite = SameSiteMode.None; });
2. If you are using cookie authentication without ASP.NET Core identity you can turn off the protection with the following code
services.AddCookie(CookieAuthenticationDefaults.AuthenticationScheme, options => {
// Other options
options.Cookie.SameSite = Microsoft.AspNetCore.Http.SameSiteMode.None; })
3. If you are using external OIDC providers you may be able to avoid the issue by changing the response mode your provider uses from a POST to a GET request, using the following code. Not all providers may support this.
.AddOpenIdConnect("your_OIDProvider", options => {
// Other options
options.ResponseType = "code";
options.ResponseMode = "query";
};
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best Regards,
Jason