Hi All,
Some of our users are not able to log in to our web api which uses ADAL to authenticate against Azure AD. For example, they receive this error message:
AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user's session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge,
and the web app sending the silent sign-in request is in different IE security zone than the Azure AD endpoint (login.microsoftonline.com).
Trace ID: 347084b6-97f3-4893-996a-8a62b7734baa
Correlation ID: 363a3961-6701-4ef1-9509-75a319d96d98
Timestamp: 2016-11-23 20:25:06Z
I've narrowed it down to users created in one directory which are then added to another directory. The error only occurs for users added to the second directory in the last few weeks. Other users that were added before work correctly.
This recent thread discusses a similar issue, which seems resolved, but ours is ongoing:
https://social.msdn.microsoft.com/Forums/en-US/7e985e74-4cd2-4407-88e6-dfb4cceae85d/the-infamous-aadsts50058-error-when-using-external-accounts-in-azure-ad-tenant?forum=WindowsAzureAD
I've opened a support ticket in the Azure portal but so far, no response. Any suggestions are welcome.
Thanks,
Andrew
Some of our users are not able to log in to our web api which uses ADAL to authenticate against Azure AD. For example, they receive this error message:
AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user's session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge,
and the web app sending the silent sign-in request is in different IE security zone than the Azure AD endpoint (login.microsoftonline.com).
Trace ID: 347084b6-97f3-4893-996a-8a62b7734baa
Correlation ID: 363a3961-6701-4ef1-9509-75a319d96d98
Timestamp: 2016-11-23 20:25:06Z
I've narrowed it down to users created in one directory which are then added to another directory. The error only occurs for users added to the second directory in the last few weeks. Other users that were added before work correctly.
This recent thread discusses a similar issue, which seems resolved, but ours is ongoing:
https://social.msdn.microsoft.com/Forums/en-US/7e985e74-4cd2-4407-88e6-dfb4cceae85d/the-infamous-aadsts50058-error-when-using-external-accounts-in-azure-ad-tenant?forum=WindowsAzureAD
I've opened a support ticket in the Azure portal but so far, no response. Any suggestions are welcome.
Thanks,
Andrew