The Future of Identity (Keystone)
summary
Roadmap lists concrete changes not marketing: v3 everywhere replaces v2, federation adds OpenID Connect alongside SAML, direct x509 client certs auth aims to remove bearer tokens, and fernet tokens replace uuid/pki tokens (compact AES+HMAC format, revocation currently slow). Stack moves code toward Flask and a standalone keystone auth library, removes keystoneclient CLI in favor of openstack client, and implements hierarchical projects and a reseller mode; priorities are technical debt paydown, stability, and measurable token size and storage improvements.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:46What is the future direction of OpenStack Identity?
- 5:03Fernet Tokens!
- 15:38Keystone Client
- 21:44Questions?
related talks
15mImprovements to Identity Federation in Keystone
32mPlatform Security that will Last for Decades
01h 12mIdentity 2.0: the what, why and how of social and federated login
19mIdentity:The missing link in API security
27mFrom AuthN to AuthZ: The Future of Identity
32mModern And Secure IAM For Modern Applications
31mCloud Foundry UAA as an Identity Proxy Product Roadmap
04mYou Don't Need a New Identity Platform for the AI Era