Icinga for Windows v1.13.0 - Beta Feedback Thread

[cstein (Lord Hepipud)]

Hello everyone and welcome to the Icinga for Windows v1.13.0 Beta feedback thread!

As we have mentioned in our recent blog post regarding Icinga for Windows, we are currently running a beta phase for v1.13.0 to ensure everything is working as expected.

We would love to hear your feedback and your experience as well as issues, problems and things you would like to see improved. Please share in case of problems as much details as possible, allowing us to better troubleshot these issues.

How to install the beta

On existing Icinga for Windows installations, you can simply add the beta repository:

Add-IcingaRepository -Name 'Icinga Beta' -RemotePath 'https://packages.icinga.com/IcingaForWindows/beta/ifw.repo.json';

Once done, you can use

Update-Icinga -Confirm;

to install the latest beta versions.

For the changelog for each beta release, you can check out the GitHub release page for

• Framework
• Plugins

Thank you for your feedback and your contribution!

Edit 2024-09-19: Beta 2 of the Framework has been released!

[lrk]

Hi @cstein

You have added new commands to stop and start Icinga and Icinga for Windows.
I think it would be good if there was also a command to update the JEA service user password, especially because of policies.

Because when I run the Install-IcingaSecurity -IcingaUser ‘CustomIcingaUser’ a second time, the services no longer work.
I then have to manually set a new password for the local user in computer management and enter it in the two services and start the services, then it works again.

Thanks for the improvements so far!

[cstein (Lord Hepipud)]

Hello

Thank you for your feedback. There is already a solution available to achieve this, which is not documented as I personally feel using passwords directly by using the CLI are not a good idea.

How ever, here is what you can do to achieve this:

[SecureString]$Password = Read-Host -AsSecureString;
Set-IcingaInternalPowerShellServicePassword -Password $Password;

In case you want to automate it, you can run it like this (not recommended, because the password is then stored in the history):

Set-IcingaInternalPowerShellServicePassword -Password (ConvertTo-IcingaSecureString 'mysecretpassword');

For security reasons with the below example I would recommend this in addition:

Clear-History;
[Microsoft.PowerShell.PSConsoleReadLine]::ClearHistory();

If this works for you, I would appreciate the feedback. Adding this to the docs as possibility should be fine.

[lrk]

Hi @cstein

thanks for your solution I have now created the following script:

Use-Icinga

$User = Get-IcingaPowerShellConfig -Path 'Framework.Icinga.ServiceUser';

Set-LocalUser -Name 'customUser' -Password (New-IcingaWindowsUserPassword)

Set-IcingaServiceUser -User $User -Password $Global:Icinga.ServiceUserPassword -Service 'icinga2' | Out-Null;
Set-IcingaServiceUser -User $User -Password $Global:Icinga.ServiceUserPassword -Service 'icingapowershell' | Out-Null;

Clear-IcingaWindowsUserPassword;

[lrk]

Hello all

I may have another topic, that is, if you enter passwords here you have to escape $.
Would it be possible that passwords are not interpreted by PowerShell?

[moreamazingnick]

@lrk

if you enter passwords here you have to escape $

That is an “Icinga thing” for variables. Since variables can reference other variables $ has to be escaped by another $

How do I escape a password ending with a dollar sign icinga2?

[lrk]

Hi @moreamazingnick

thanks for your feedback, I didn’t think of that
Looks like we need a new data type “Password”

[moreamazingnick]

You could use string → visible hidden, and that’s a director thing not a powershell framework thing

[lrk]

then maybe there should be an option that no variables are taken into account.
But I’m quiet now, sorry, don’t want to mess up this topic with my problems.

[rivad (Dominik)]

It would be nice, if the Director escapes the $s in hidden fields

[drapiti (Denis)]

Hi @cstein, Hi all, When we try to install the powershell service using the Icinga Beta 1.13 we are getting the following error.

Any idea what the issue may be? Same command works perfectly for version 1.12.3 of the framework.