7,023 questions
ADFS Authentication Failing in Chrome: MSISConext Cookie Issue
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 44%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
Sandeep Gaur
15
Reputation points
We are using ADFS to redirect authentication to our underlying IDP. Previously, we ran our app within an iframe of another app, and it worked fine. However, with Chrome’s recent changes regarding third-party cookies, we are now facing issues.
Upon debugging, we found that the failure is due to the inability to get the MSISConext cookie. Are there any plans to enhance ADFS to include additional parameters like ‘Partitioned’ to allow the MSISConext cookie to be saved?
Additionally, is there any temporary workaround for this problem?
Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Microsoft Security | Active Directory Federation Services
1,314 questions
{count} votes
-
Sandeep Gaur 15 Reputation points
2024-11-18T02:14:00.2266667+00:00 Error in logs: Encountered error during federation passive request. Additional Data Protocol Name: Saml Relying Party: Exception details: Microsoft.IdentityServer.Web.CookieManagers.InvalidContextException: MSIS7001: The passive protocol context was not found or not valid. If the context was stored in cookies, the cookies that were presented by the client were not valid. Ensure that the client browser is configured to accept cookies from this website and retry this reques
Sign in to comment
Sign in to answer