Icinga / Icinga/icinga-powershell-framework
JEA username and domain
@LordHepipud is already working on this.
Since Jan 28, 2023.
- Dominant language
- PowerShell
- Stars
- 87
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
During environment setup in the "Icinga for Windows Management Console" I was selecting the option "Install JEA Profile with managed user "icinga"". This basically runs fine for all checks, but during the checks of MSSQL I found the following issue.
When running the MSSQL checks with IntegratedSecurity on, the login attempt fails. During my investigations I saw Icinga using the server's name as username and the domain as domain (so, login attempt is done with "[domain][server name]$", but it should be [server name]\icinga; this local user has all needed permissions in the database).
Expected Behavior
The check should be green.
Current Behavior
The check fails due to DB connection error.
Steps to Reproduce (for bugs)
- Start JEA test environment
- Execute an MSSQL check (in my case, it's either
invoke-IcingaCheckMSSQLHealth -IntegratedSecurity true -warning 1s -critical 2s(which returns DB connection error and is red) orInvoke-IcingaCheckMSSQLBackupStatus -IntegratedSecurity(which returns an Icinga error with the above mentioned user credentials and is violet) - Besides that, typing
$env:usernameshows the server name together with the $ sign and$env:userdomainshows the domain name. So it's at least not an issue of the MSSQL plugins.
Your Environment
- PowerShell Version used (
$PSVersionTable.PSVersion): 7.3.0 - Windows Server 2022 (10.0.20348)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.