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
MSAL currently requires localAccountId only in JS when one specifies an account through the configuration options. This value is returned from the account information we receive on the response objects. In .Net, this value is not returned on the response objects and not required.
As part of this PR #14064 I have made the workaround of re-using the homeAccountId to fulfill the localAccountId requirement. This does work, but the MSAL team tells me this is not correct and a real localAccountId is necessary for authentications such as ADSF.
I am not sure whether they should make this optional or require it in all languages. In any case, we probably shouldn't be using the homeAccountId as a replacement value anyway.
MSAL currently requires localAccountId only in JS when one specifies an account through the configuration options. This value is returned from the account information we receive on the response objects. In .Net, this value is not returned on the response objects and not required.
As part of this PR #14064 I have made the workaround of re-using the homeAccountId to fulfill the localAccountId requirement. This does work, but the MSAL team tells me this is not correct and a real localAccountId is necessary for authentications such as ADSF.
I am not sure whether they should make this optional or require it in all languages. In any case, we probably shouldn't be using the homeAccountId as a replacement value anyway.
External issue: AzureAD/microsoft-authentication-library-for-js#3336
The text was updated successfully, but these errors were encountered: