Authenticate to Cockpit from anywhere
summary
Browser front end runs on one unprivileged process while the actual session runs where root access is needed: components are cockpit-ws, cockpit-session, cockpit-bridge passing a JSON pipe. Authentication works with passwords, SSH keys, Kerberos/Identity Management tickets (single sign‑on), and TLS client certs (smart cards); Foreman/Satellite embeds Cockpit via a reverse proxy and a bastion host proxy pattern so thousands of servers need no per‑host webserver. A desktop helper launches a network-namespace browser to sandbox the UI; sudo/polkit two‑factor flows are still limited.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:13Cockpit
- 0:43Log into Cockpit
- 1:36Cockpit on Windows 10
- 3:36Cockpit Components
- 5:36Cockpit Session
- 9:06Bastion
- 10:23Other authentication
- 18:08Conclusion
- 18:34Questions
related talks
17mYour-turn key Cockpit UI in a CICD ecosystem
50m.NET Rocks Live
33mFirst-Class Auth Experience In Frontend Applications
22mEnsuring Platform Security with Windows Bosh Add-ons - Maris, Schaefbauer, Coppock, Boeing
40mGoing passwordless with Web Authentication
21mDon't Be Afraid to Operate Alone! The ABCs of Authentication Infrastructure Management
39mAuthN and AuthZ at Cruise: Crawl, Walk, Run
02mScalable Infrastructure Access Management