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
My app has a multi auth scheme (custom cookie scheme + AddMicrosoftIdentityWebApp()). The second scheme should be optional and is only used to authenticate calls to MS Graph API. Whenever I am signing in with my MS account though and it redirects back to my application it overwrites the HttpContext.User (removing all claims etc). Is there any way to prevent that? Would it be possible to instead add an additional identity via ClaimsPrincipal.AddIdentity()?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My app has a multi auth scheme (custom cookie scheme +
AddMicrosoftIdentityWebApp()). The second scheme should be optional and is only used to authenticate calls to MS Graph API. Whenever I am signing in with my MS account though and it redirects back to my application it overwrites theHttpContext.User(removing all claims etc). Is there any way to prevent that? Would it be possible to instead add an additional identity viaClaimsPrincipal.AddIdentity()?Beta Was this translation helpful? Give feedback.
All reactions