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
If the Balzor-Seite is embedded in an IFrame (Microsoft Teams WebsiteTab) the Authentication ends up in a Loop.
Teams uses also Federated Authentication with Okta.
Using the Site Standalone the Authentication Works as aspect.
AccountController is called -> Challange is Called -> Okta Login does appear
OnTokenValidateEvent gets fired containing the authenticated Userprincipal in args.Identity
AccountController is called -> HttpContext.User is authenticated
Using the same Site in a Team Websitetab the steps are the following:
AccountController is called -> Challenge is Called -> no Okta Login appears (Token is already here)
OnTokenValidateEvent gets fired containing the authenticated Userprincipal
AccountController is called -> but now User is not authenticated! --> Loop
If the Balzor-Seite is embedded in an IFrame (Microsoft Teams WebsiteTab) the Authentication ends up in a Loop.


Teams uses also Federated Authentication with Okta.
Using the Site Standalone the Authentication Works as aspect.
AccountController is called -> Challange is Called -> Okta Login does appear
OnTokenValidateEvent gets fired containing the authenticated Userprincipal in args.Identity
AccountController is called -> HttpContext.User is authenticated
Using the same Site in a Team Websitetab the steps are the following:



AccountController is called -> Challenge is Called -> no Okta Login appears (Token is already here)
OnTokenValidateEvent gets fired containing the authenticated Userprincipal
AccountController is called -> but now User is not authenticated! --> Loop
This is the Configuration used:
