ZITADEL

I'm in the middle of ZITADEL integration. It's going well so far. The local environment is set up with Docker. Everything looks good. I'm preparing my .NET Core backend webhook to handle registration events from Zitadel. I want to make sure that when a user signs up or logs in through Zitadel, the backend can process those events correctly and maintain the user data in sync. Other users' profile changes also should go smoothly with the same approach. All auth sign-ups and sign-ins will be handled by Zitadel, so I can focus on the core business logic and user experience without worrying about the complexities of authentication and security. Moreover, I can use this in my other future projects as well. #LIFOCode #SoftwareEngineering #Modernization #Authentication #Zitadel

Think Like a Hacker: Highlights from HackingLab Day 2026 We had an incredible time sponsoring HackingLab Day 2026 at the START Global Campus in St. Gallen! In collaboration with the Universität St.Gallen (HSG) and GObugfree AG, we dove deep into the future of cybersecurity. The capture the flag was a highlight of the day. Check out our full recap! https://lnkd.in/eD3WfPXb Thanks to Christoph Bühler Guido Salvaneschi Nadine Anderson for the well organized event 👏 #CyberSecurity #STARTGlobal #ZITADEL #AI #EthicalHacking #InfoSec #HSG

Complexity shouldn't be the status quo. We’ve heard your feedback on naming inconsistencies in ZITADEL. Today, we’re taking a major step toward a more intuitive developer experience with a platform-wide terminology alignment. Standardized docs. Unified UI. Zero breaking changes. Read the full announcement and see the mapping on our blog: 👉 https://lnkd.in/eduvzZGx #DeveloperExperience #IAM #OpenSource

Are you ready to think like a hacker? We're sponsoring a HackingLab Day on March 27th at the START Global Campus in St. Gallen. It's a hands-on day with a practical introduction to ethical hacking. Explore the legal framework, learn the tools and techniques security teams use in the real world, and put your skills to the test in a capture-the-flag challenge. 🚩 Register now: https://lnkd.in/exijJMfG

Integrating Linux fleets with modern identity providers has historically required maintaining LDAP bridges or complex SSSD configurations. Ubuntu's latest update to AuthD changes this architectural requirement by introducing a generic OIDC broker. You can now authenticate Ubuntu environments directly against an OIDC provider like ZITADEL. This removes the need to maintain legacy directory services purely for OS-level access control. By treating the OS login as a standard OIDC client, we reduce the attack surface, remove protocol translation layers, and simplify the provisioning pipeline. https://lnkd.in/e-Dm_m85 #Linux #OIDC #DevOps

Disconnected traces in an authentication flow turn debugging into a guessing game. Historically, ZITADEL’s core Go backend supported OpenTelemetry, but the user-facing Login UI operated as an observability black box. Your ingress would initiate a trace, the Login UI would drop the context, and the backend would spin up a new one. A single user request resulted in fragmented telemetry data across the edge and the database. With PR #11429 (which we plan to land in v4.13.0), we are rolling out end-to-end distributed tracing. We implemented a custom gRPC interceptor in the Login UI to propagate W3C trace context directly to the ZITADEL backend. A single trace now accurately maps the entire transaction from the initial HTTP request through the authentication attempt down to the gRPC handler. We also replaced standard console output in the Login with structured JSON logging to automatically inject trace IDs for exact log correlation, and exposed Node.js runtime metrics. You cannot reliably operate infrastructure you cannot observe. This update ensures your telemetry actually reflects the complete request lifecycle. Interested in the code? Check the PR https://lnkd.in/g9-_9hzK #OpenTelemetry #DistributedTracing #Identity #Auth #opensource

It has been a while since I checked the GitHub trending repositories, but out of sheer interest I took a look today and it brought me a lot of joy to see ZITADEL back on the daily Go list. Building an open-source identity provider means spending most of your time buried in OIDC and SAML specs, dealing multi-tenant data isolation, and generally optimizing our product for security, reliability and usability. It's infrastructure plumbing that usually only gets noticed when something breaks. Seeing this kind of interest from the developer community is a great reminder that the architectural decisions we are making are resonating with other builders. Thank you to the community for reading the code, submitting the brutal (but necessary) GitHub issues, and helping us refine the core engine. Back to work.

I love to read this! "ZITADEL is the best modern alternative to Keycloak for self-hosted identity management..."

ZITADEL v4.12.0 got published and my small, but favorit change is that we now also support end to end TLS for the new Login UI! https://lnkd.in/gsz9Z24g