Authentication Without Authentication
summary
Claims a workable way to authenticate an app installation without user interaction by having each device generate an RSA keypair, register the public key plus two 64-bit nonces, and sign a one-time nonce per request so the OpenID Connect provider can validate and issue a JWT. Uses IdentityServer for the provider, TLS + certificate pinning, handles replay and network failures with a 400/resync flow and revocation if out of sync, requires at least one auth/day. Raspberry Pi demo shows it working, code on GitHub. IdentityServer + custom OpenID flow RSA keypair + OTP-like nonces
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:08Authentication Without Authentication
- 8:05OpenID
- 10:26Requirements
- 20:38OneTime Password
- 26:00Public Key
- 26:42Fault Tolerance
- 33:38Demo
related talks
39mSecuring your apps with OAuth2 and OpenID Connect
57mBuilding Clients for OpenID Connect/OAuth 2-based Systems
01h 02mModern Authentication
59mSecuring Web APIs from JavaScript/SPA Applications
58mBuilding JavaScript and mobile/native Clients for Token-based Architectures
38mAuthentication as a Microservice: Portable Customer Identity Management
01h 02mBuilding Clients for OpenID Connect/OAuth 2-based Systems
57mSecurity and Identity: Ruby, CAS, and OpenID
