Having trouble reading this email? Click here.

 

SUMMARY

Hi [First Name],

New security features for Icinga Web, a bugfix release for Icinga 2, new posts from the blog, and we are Gold Sponsor at OSMC 2026.

Happy Reading!

Three new features are available for Icinga Web that together cover the most common access security requirements:

• Icinga SSO adds single sign-on support to Icinga Web.
• Icinga TOTP Web adds time-based two-factor authentication - users enroll once and provide a 6-digit token on every login.
• Password Policies lets administrators enforce configurable password rules, with built-in BSI and PCI-DSS-aligned presets.

RELEASE OVERVIEW

Icinga Web 2.14, Security Releases, and Module Updates

Icinga Web 2.14 adds the extension point for two-factor authentication, configurable password policies, and a dynamically assembled Content Security Policy header. Icinga Certificate Monitoring 1.4, Icinga Reporting 1.1, and Icinga PDF Export 0.13 ship alongside it with PHP 8.5 support. If you are still on 2.12.x or 2.13.x, security releases 2.12.7 and 2.13.1 close an open redirect vulnerability - check the release announcement and treat them as a priority update.

Icinga 2 v2.16.3, v2.15.5, and v2.14.10

The June security releases introduced an unintended regression: an internal change caused a required argument to appear in the DSL's Json.decode() function, breaking existing configurations that called it with a single argument. These releases revert that behavior. If you are running v2.16.2, v2.15.4, or v2.14.9, upgrade to the latest patch release.

BLOG

Building a Shared Icon and Font Library for Icinga Web

 

If you have copied the same icon font into two or three Icinga Web modules, this post is for you. It covers how to build a self-contained shared library with a composer.json manifest, PSR-4 autoloading, bundled LESS and JS, and static assets any module can reuse.

Specifics in Packaging Icinga Go Applications

 

Why are there seven Icinga DB v1.5.1 packages? This post explains what makes Go application packaging different - and why every Go security fix triggers a new release.

COMMUNITY CORNER

We are a Gold Sponsor of OSMC 2026 - and this year the conference celebrates its 20th anniversary. Three days, more than 30 talks, three workshops, and the hallway conversations that make it worth attending. Still need a ticket? 

Use code ICINGA20@OSMC_2026 for 20% off at osmc.de/tickets.

Service Object Name Too Long After Upgrading to 2.16

After upgrading to 2.16, a user saw a flood of warnings about service names exceeding 255 characters - even though the names looked short. The root cause: apply for rules iterating over arrays use the full dictionary as the name identifier. Switching to dictionary iteration with name => port resolves it.

Array Data Fields Search in Icinga Director

A user migrating from Icinga 1 ran into unexpected search behavior with array-type custom variables in Director - hosts with multiple values assigned weren't showing up as expected. Still open: if you have knowledge on the topic, your input would be welcome.

Migrating Windows Plugins to PowerShell Plugins

A user wanted to replace classic Windows plugins with PowerShell plugins in config files rather than Director. The thread covers how Icinga for Windows needs to be installed on the target machines and how to generate DSL config files - useful if you're planning the same migration.

NEED ANYTHING ELSE?

Monitoring is a long-term investment. We offer training, consulting, and direct support to help your team get the most out of Icinga - whether you're just getting started or running it at scale. 

You made it to the end of this newsletter!

If you have any questions, feedback or anything you would like us to cover in the next newsletter, don't hesitate to get in touch. 

 

Until next month, 
Angelika and the Icinga Team

How would you rate this month's newsletter?

 

FOLLOW US

 

If this message is not displayed properly, click here please.

Icinga GmbH 
Deutschherrnstr. 15-19 
90429 Nuremberg 
Germany 

+49 911 9288555 
info@icinga.com 
https://icinga.com 
CEO: Julian Hein, Bernd Erk 
Register: Nuremberg 
Tax ID: DE318593083 

If you don't want to receive any more messages (to: [Email]), you can manage your preferences.