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
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
Change the appsetttings.json to set tenantId to a GUID (to have a tenanted authority). This only reproes with a single tenant app
sign-in to the app with a guest user
try to call Contact
Any log messages given by the failure
There is an infinite loop
Expected/desired behavior
you can see the information about the signed-in user
OS and Version?
Chrome
Versions
Mention any other details that might be useful
When calling the controller, the cache is empty. This is because the cache is keyed by the MSAL.id, and the computation of the MSAL.id is not right in the case of a guest user (tid and iod are the guest ones, not the home tenant information).
The text was updated successfully, but these errors were encountered:
jmprieur
changed the title
GetMsalAccountId does not retrieve the right value for guest users in sigle tenant apps
Infinite loop when signing-in with a guest account in a single tenant application
Dec 10, 2018
For the moment, fixed the issue with special processing for guest users
however.
GetMsalAccountId does not retrieve the right value for guest users in sigle tenant apps. Getting the home tenant id and home oid would require one more call to the STS.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
There is an infinite loop
Expected/desired behavior
you can see the information about the signed-in user
OS and Version?
Chrome
Versions
Mention any other details that might be useful
When calling the controller, the cache is empty. This is because the cache is keyed by the MSAL.id, and the computation of the MSAL.id is not right in the case of a guest user (tid and iod are the guest ones, not the home tenant information).
The text was updated successfully, but these errors were encountered: