.NET Rocks Live
summary
Practical answers for real integration: desktop apps achieve single sign‑on by launching the system browser SSO (GitHub for Windows example) so shared cookies return tokens; headless devices use the device flow (e.g., Nintendo Switch pattern); APIs can require mutual TLS plus sender‑constrained access tokens for device identity (medical scenario); PKCE mitigates code‑substitution attacks; updated JavaScript guidance and CSP advice reduce token leakage; IdentityServer shows 157 contributors and Microsoft is shipping zero‑config identity templates in .NET Core preview.
AI-written summary · about
chapters (8)
- 0:00Start
- 17:29What Makes Spa's Different from a Security Context
- 20:39Injection Attacks
- 20:57Cross-Site Scripting
- 21:17Content Injection
- 24:42Turn Off Inline Javascript
- 27:37Substitution Attacks
- 46:26Distributed Identity Foundation
related talks
39mSecuring your apps with OAuth2 and OpenID Connect
59mThe whirlwind tour of Authentication and Authorization with ASP.NET Core
54mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
51mAuthentication and Authorization in ASP.NET Core 2
45mOAuth and beyond: Modern auth not only for the web
01h 03mSecuring Web Applications and APIs with ASP.NET Core 2.2 and 3.0
58mBuilding JavaScript and mobile/native Clients for Token-based Architectures
58mSecurity in ASP.NET Core 2.0
