Skip to content
This repository has been archived by the owner on Jun 26, 2021. It is now read-only.

After blocking third party cookies in the browser, browser treating login.microsoftonline.com as third party cookies and blocking it. #900

Closed
m-sunilkumar opened this issue Apr 24, 2020 · 4 comments

Comments

@m-sunilkumar
Copy link

After blocking third party cookies in the browser.Login is not happening because "login.microsoftonline.com" is blocked to set cookies as it is treated as third party cookies.Is there any way to configure the authentication setup so that "login.microsoftonline.com" will not be treated as third party cookies and login actually happens even with blocked third party cookie settings. I have used react-adal for authentication service with standard adal-config object with client id ,tenant-id,and cacheLocation.
how i can allow this login.microsoftonline site to set cookies even with third party cookies block from client side script.
adalConfig = {
// instance: https://login.microsoftonline.com/${tenantid}/,
tenant: tenantid,
clientId: clientId,
redirectUri: redirectUri,
endpoints: {},
cacheLocation: "sessionStorage",
extraQueryParameter: "scope=openid,https://graph.microsoft.com/.default"
};

using authContext object iam handling login process.
authContext = new AuthenticationContext(adalConfig);

Please help me with this to solve this third party cookie problem

Browser:chrome

@Mhbuur
Copy link

Mhbuur commented Jun 17, 2020

Facing the same challenge here.

The browser development trend of blocking third party cookies is on a rise. Recently Chrome launched an update blocking third party cookies in In Cognito mode by default, and Mozilla is taking it further for standard sessions too.

https://venturebeat.com/2020/05/19/google-chrome-83/

https://venturebeat.com/2019/06/04/firefox-enhanced-tracking-protection-blocks-third-party-cookies-by-default/

How do we get around this without telling the clients to add "login.microsoftonline.com" to trusted sites?

@jasonnutter
Copy link
Contributor

We are solving this for most scenarios in MSAL.js v2 by switching from the Auth Code Flow. See AzureAD/microsoft-authentication-library-for-js#1000 for more details (this work will not be done ADAL.js).

@Mhbuur
Copy link

Mhbuur commented Jun 18, 2020

@jasonnutter so no updates to ADAL in this regard?

@jasonnutter
Copy link
Contributor

@jasonnutter so no updates to ADAL in this regard?

No, you will need to upgrade to MSAL.js v2 to address problems with third-party cookies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants