Closed niwsa closed 4 years ago
@niwsa Thanks for posting this. We have looked at the Storage API and we are currently exploring options that will require changes to both the auth client library and server.
The current workaround we are using is to introduce the authorization code flow for browsers, which limits the usage of iframes. We have introduced this in the @azure/msal-browser package which is currently in beta. We recommend using this package to get token exchange working in Safari browsers.
@pkanher617 Thanks for the reply.However I understand that @azure/msal-browser is not available for B2C tenants which is really my use case.For now thinking of using https://github.com/AzureAD/passport-azure-ad with server side rendering (Next JS).
@niwsa We are hoping to have support for B2C tenants by the end of this month, keep an eye out for new releases!
@pkanher617 - re your comment on 14th May - are B2C tenants now supported please?
Library
msal@1.x.x
or@azure/msal@1.x.x
@azure/msal-browser@2.x.x
@azure/msal-angular@0.x.x
@azure/msal-angular@1.x.x
@azure/msal-angularjs@1.x.x
Description
Current work around for silent token renewal failure in safari requires user intervention i.e to completely disable the third party cookie blocking in Safari Preferences.However it appears a better alternative exists in the form of Storage Access API.
From MDN doc
From webkit blog
Is this something we can look into as a possible alternative ?