Skip to content

Release v1.0.22

Choose a tag to compare

View all tags
@jullienl jullienl released this 05 Feb 09:01
· 18 commits to main since this release
v1.0.22
daead27

🎯 What's New in v1.0.22

Enhancements

UTF-8 Character Support

All Cmdlets - Proper Handling of Accented Characters

  • Fixed issue where names and text with accented characters (é, à, ñ, etc.) were corrupted
  • Affects all cmdlets that send or receive text data (Get-HPEGLUser, New-HPEGLLocation, New-HPECOMGroup, etc.)
  • Characters now display and send correctly in all operations

Error Handling - Improved User Guidance

Connect-HPEGL - Enhanced Error Messages

  • SSO Detection: When using -Credential with hpe.com account requiring SSO, error now clearly directs to use -SSOEmail instead
  • Authentication Context: Error messages now reflect the actual authenticator in use (password vs Okta Verify)
  • User Identifier Validation: Improved detection of SSO redirect scenarios to prevent misleading "username not recognized" errors
  • 401 Errors: Password authentication failures now show "Incorrect password or authentication error" instead of generic Okta Verify message
  • Entra ID State 3: Added specific error handling for AuthorizationState = 3 (passwordless not fully configured) with clear setup instructions

Invoke-EntraIDMFAAuthentication - Enhanced Push Notification Handling

  • State 3 Detection: Now properly identifies when Microsoft Authenticator is installed but passwordless phone sign-in is not enabled
  • Clear Guidance: Provides step-by-step instructions for enabling passwordless sign-in (phone sign-in toggle)
  • Alternative Options: Suggests using -Credential parameter as immediate workaround
  • Better Diagnostics: Distinguishes between denied push (State 1), approved (State 2), not configured (State 3), and unexpected states

iLO Connection - DisabledByCOM Handling Fix

Connect-HPEGLDeviceComputeiLOtoCOM - Fixed False Connection Failures

  • Issue Fixed: iLOs showing DisabledByCOM status with WebConnectivity: Connected were incorrectly reported as failed connections
  • Root Cause: DisabledByCOM is a temporary administrative state during initial connection establishment, not a failure
  • Solution:
    • Excluded DisabledByCOM from error detection logic
    • Modified loop exit condition to recognize successful connection when DisabledByCOM + Connected state detected
    • Connection now properly proceeds to verify device appears in workspace
  • Impact: iLO connections that were failing with "iLO cannot be connected to Compute Ops Management! DisabledByCOM" now correctly complete as successful
  • Result: Status now shows "Complete" with device successfully appearing in COM workspace

Unicode Character Support - UTF-8 Encoding Fix

Invoke-HPEGLWebRequest & Invoke-HPECOMWebRequest - Fixed Character Encoding

  • Issue Fixed: API calls with accented characters (é, à, ü, ñ, etc.) in JSON payloads were being corrupted in both requests and responses, causing validation failures

  • Root Cause:

    • Sending: JSON strings with non-ASCII characters weren't properly UTF-8 encoded before transmission
    • Receiving: API responses with accented characters weren't explicitly decoded as UTF-8, resulting in corruption (é became ??)

  • Affected Cmdlets: Any cmdlet sending/receiving user names, descriptions, or text fields with accented characters:

    • Get-HPEGLUser - Returned corrupted names ("Lion??l" instead of "Lionél")
    • New-HPEGLLocation - Failed when contact emails referenced users with accented names
    • New-HPECOMGroup - Could fail with accented group descriptions
    • All other cmdlets using Invoke-HPEGLWebRequest or Invoke-HPECOMWebRequest

  • Solution:

    • Request Encoding: Automatic detection of non-ASCII characters, converts JSON payloads to UTF-8 byte arrays before sending
    • Response Decoding: Explicit UTF-8 decoding of API responses using RawContentStream with StreamReader
    • Applied to all API endpoints in both wrapper functions (UI Doorway, GLP Platform API, Onepass API, COM API)

  • Example Errors Resolved:

  • Impact: All cmdlets now properly handle international characters in both directions (API → PowerShell and PowerShell → API)

  • Result: Users with accented characters work correctly in all operations - retrieving user data, creating locations, group descriptions, etc.

Breaking Changes

None

Deprecations

None

Installation & Upgrade

PowerShell Gallery

# Install or update to latest version
Install-Module -Name HPECOMCmdlets -Force

# Update existing installation
Update-Module -Name HPECOMCmdlets

Minimum Requirements

  • PowerShell 7.0 or later
  • HPE GreenLake account with Compute Ops Management service provisioned

Resources

Assets 2
Loading