HewlettPackard / HewlettPackard/PowerShell-ProLiant-SDK
Set-HPEiLODirectorySetting wrong DirectoryServerAddress in HPEiLOCmdlets 4.0.0.0
- Dominant language
- PowerShell
- Stars
- 97
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
# Issue
Set-HPEiLODirectorySetting add port number in DirectoryServerAddress
In iLO web GUI the DirectoryServerAddress is shown with added port number.
Get-HPEiLODirectorySetting show correct address without port
Users can not login with domain account until the port number is removed from DirectoryServerAddress in web GUI.

## Example
```powershell
Set-HPEiLODirectorySetting -Connection $connectioniLO -DirectoryServerAddress ilo.domain.corp -LDAPDirectoryAuthentication -DirectoryServerPort 636 ...
```
## Logs
### Module version
```powershell
PS C:\scripts> Get-Module HPEiLOCmdlets
ModuleType Version Name
---------- ------- ----
Binary 4.0.0.0 HPEiLOCmdlets
```
### Server model and firmware
```powershell
PS C:\scripts> $connectioniLO.TargetInfo
ProductName : ProLiant ML110 Gen10
ServerFamily : ProLiant
ServerGeneration : Gen10
ServerModel : ML110
iLOGeneration : iLO5
iLOFirmwareVersion : 2,78
SystemROM : U33 v2.68 (07/14/2022)
ProcessorName : Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz
```
### Output by commandlet
```powershell
PS C:\scripts> (Get-HPEiLODirectorySetting -Connection $connectioniLO)
DirectoryServerAddress : ilo.domain.corp
DirectoryServerPort : 636
GenericLDAPEnabled : Yes
LDAPDirectoryAuthentication : DefaultSchema
LocalUserAccountEnabled : Yes
LOMObjectDN :
UserContext : {@domain.corp}
IP : 10.5.3.197
Hostname : ilo.domain.corp
Status : OK
StatusInfo :
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue with Set-HPEiLODirectorySetting using DirectoryServerAddress ilo.domain.corp and DirectoryServerPort 636, then compare its result with Get-HPEiLODirectorySetting and the iLO web GUI. Done means the configured address remains without the port while directory authentication continues to work; the payload does not identify an implementation file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100