
Welcome to Advanced Zero Trust Architectures with OpenZiti 2.0. Learn about the instructor's background, who this course is designed for, and how the hands-on lab environment is structured.
An executive tour of the key architectural evolutions in OpenZiti 2.0, including HA-native RAFT control planes, JWT-based authentication, and OIDC enrollment.
Walk through the 12-module advanced syllabus, lab requirements, and role-based learning paths for security engineers and cloud architects.
Explore how RAFT consensus powers the OpenZiti 2.0 control plane: quorum calculations, automated leader elections, preferred leader failovers, snapshot compaction, rate-limiting knobs, and the critical isleader health monitoring endpoint.
Understand the two replication boundaries in OpenZiti 2.0: full state replication between controllers via RAFT versus the bespoke data slice delivered to edge routers to enable high-throughput, local authorization decisions.
Walk through the end-to-end 2.0 token flow: token issuance via OIDC endpoints, custom OpenZiti claims (z_cfs, z_acf), and distributed local verification at the router boundary without controller roundtrips.
Correction: this lecture describes Module 12 as a zero-downtime upgrade that also covers moving a pre-2.0 cluster. Module 12 is the upgrade from OpenZiti 2.0.3 to 2.0.6. While the controllers are on mixed versions, the cluster refuses changes for about a minute (the read-only window); reads and traffic keep working.
Correction: the lesson roadmap numbers two lessons wrongly. The failure drills are Lesson 06 and the operability wrap is Lesson 07.
Note: the "healthy cluster" slide shows the controllers on v2.0.0. The course pins v2.0.3, so your ziti agent cluster list shows v2.0.3. The slide PDF in the resources is updated.
Correction: one slide shows sudo systemctl stop openziti-controller. The service is named ziti-controller: use sudo systemctl stop ziti-controller. The lab guide has the right command.
Correction: the video says routers listen for links on port 6004. In this course, routers carry both client connections and router-to-router links on port 3022; the package sets this up and there is no separate link port. Lesson 03 and the lab guide use 3022.
Correction: the video says routers listen for links on port 6004. In this course, routers carry both client connections and router-to-router links on port 3022; the package sets this up and there is no separate link port. Lesson 03 and the lab guide use 3022.
Correction: at the end, the video says Module 11 covers the upgrade runbook. Module 11 is backup and restore; the upgrade and its runbook are in Module 12.
One compromised laptop on a VPN can reach everything on the network. In this hands-on Zero Trust Security course, you replace that VPN with Zero Trust Network Access (ZTNA) built on OpenZiti 2.0, the open-source zero-trust network, on real machines in Azure and on your own PC.
The story: you're the network engineer at Meridian Logistics, a fictional company. Every connection has to prove who it is, and reaches only the one app it's allowed to use.
What you build, module by module:
- Three OpenZiti controllers in three Azure regions (East US, Central US and West Europe), kept in agreement with the Raft protocol, so the network keeps working when a controller or a whole region goes down.
- Edge routers in Azure, and a private data center whose routers only dial out, so nothing there is opened to the internet.
- Sign-in through Microsoft Entra ID plus an OpenZiti one-time code (TOTP), with access rules for staff and partners and a device check.
- Tunnelers, the software that connects a device or an app to the network, on Ubuntu servers, in Docker containers and on Kubernetes, including apps that reach each other across clusters with no shared network.
- Monitoring with Grafana dashboards and alerts, and network events in Elasticsearch and Kibana.
- A backup you prove by restoring it, a list of when each certificate expires, and an upgrade from OpenZiti 2.0.3 to 2.0.6 while traffic keeps flowing.
- A capstone: a second region in Singapore that serves the same app from both regions.
By the end, you can design, build and run a zero-trust network that keeps working when a controller or a whole region fails, and upgrade it while traffic keeps flowing.
How the course works:
- 48 lectures in 13 modules. Modules 1–2 explain how OpenZiti 2.0 works; from Module 3 on, each module adds a piece to the same network, and most end with failure drills where you break things on purpose.
- Every lab was built and tested on real machines, in Azure and on a local PC.
- Lab guides and slides to download, module quizzes, and all lab files (OpenTofu, Docker Compose, Kubernetes manifests) in a public GitHub repository.
- The cloud labs are built with OpenTofu, so you can stop or remove machines between sessions; each lab guide ends with a cleanup section.
If you took the instructor's OpenZiti 1.0 course, it's a head start, but not a requirement.
This course is independent and not affiliated with or endorsed by the OpenZiti project.