OAuth2 on a national level - how to secure extremely sensitive apis
summary
HelseID is a national OAuth-based token service in production since 2017 used across thousands of Norwegian health organizations; baseline OAuth is declared insufficient so a narrow security profile enforces confidential clients, rejects implicit/hybrid flows, mandates PKCE and signed client keys, and moves toward DPoP (with mutual TLS as an alternative) to bind tokens to clients. Every integration requires a code review, test and production onboarding, GitHub samples, and ongoing penetration testing; the service is live and actively trusted.
AI-written summary · about
chapters (19)
- 0:00OAuth2 on a national scale
- 2:28Sensitive APIs?
- 4:16The Norwegian health sector
- 9:11But what is the problem?
- 10:01alternatives
- 11:25Securing an API is easy
- 16:51The HelseID security profile
- 18:42OAuth 2.1
- 21:29FAPI 2.0 security profile
- 23:19Standard web security
- 25:22Only confidential clients
- 29:46Keypairs only
- 32:05Strict requirements regarding signing algorithms
- 33:23Only one way to use the protocols
- 46:42USE A LIBRARY!
- 48:24code reviews
- 49:50self-service setup
- 51:25the core service
- 52:40In summary
related talks
01h 03mHelseID
01h 00mHelseID Introducing Modern Web Security in a Geriatric Health Sector
57mDeath by downtime
01h 01mSharing Health Information Through APIs
54mOAuth – the good Parts
28mBringing FIDO2 to National Identity
59mOpenID Connect & OAuth 2.0 – Security Best Practices
27mIntegrating API Security Into A Comprehensive Identity Platform
