Restricting access to IPP printers with OAuth2 framework
summary
Defines an OAuth2-based flow that adds a token exchange step so a generic IPP client obtains a short-lived endpoint access token per printer rather than exposing the main access token. Prototype exists in Chrome OS and parts land in CUPS 2.4; the client opens a browser for native OAuth, verifies printer/authorization server TLS, queries the printer for its auth server URI, and asks that server to mint per-printer tokens to reduce compromise impact.
AI-written summary · about
chapters (7)
- 0:00Introduction to project
- 1:50IPP and OAuth2 basics
- 7:30Combining IPP with OAuth2
- 11:24Security implications explained
- 23:54Token exchange solution
- 29:19Current project status
- 31:28Q&A session
related talks
54mOAuth – the good Parts
58mOAuth – the good Parts
57mThe insecurity of OAuth 2.0 in frontends
46mA Deep Dive into the Past, Present & Future of OAuth
23mThe state of OAuth
45mOAuth and beyond: Modern auth not only for the web
59mOpenID Connect & OAuth 2.0 – Security Best Practices
25mOAuth 2.1: The Future of API Security