|
Hi! This error can occur for multiple reasons:
Command used: |
Replies: 6 comments
|
Hi, Can you confirm whether your user account belongs to a domain that is configured for Entra ID SSO in your GreenLake environment? I just tested this using my Entra ID test user, and the connection to the platform was successful. Could you please generate and attach the verbose output using the following command?
|
|
Hi!
Thanks for the quick response.
My user is not part of a Entra ID SSO or any other SSO. I'm using username and password with MFA that worked like 2 weeks ago. I'm still able to logon to the GUI with this user.
unfortunately, I'm not getting any output in the verbose.txt
shell output:
Connect-HPEGL: User authentication failed.
This error can occur for multiple reasons:
1. User account does not exist in Entra ID
2. User account is disabled or locked
3. User is not assigned to the HPE GreenLake application in Entra ID
- Contact your Entra ID administrator to verify application access
- Ensure you have the required app role assignments
For complete Entra ID setup prerequisites, see: https://github.com/jullienl/HPE-COM-PowerShell-Library/blob/main/README.md
|
|
My apologies, the command to generate the verbose output was incomplete. The correct command is:
|
|
Ah thanks, now I got the output.
attached.
/Ulf
|
|
Hi Ulf, Thanks for the verbose log, it pinpointed the problem. HPE's sign-in service doesn't classify your account as either federated or local, and the library was defaulting to "federated", which sent it to your corporate identity provider instead of signing you in against your HPE account. That's why you saw the "user does not exist" message despite correct credentials. I've built a test version with a fix. It's not on the PowerShell Gallery, it installs alongside your current version and doesn't touch it. Instructions are in HOW-TO-USE.md inside the archive. In short: unblock the zip, extract it, open a new PowerShell 7 window, import the module by full path, then run Connect-HPEGL with -Verbose redirected to a file. Download: HPECOMCmdlets-1.0.27-ssofix.zip Could you send the log back either way, success or failure? If it still fails, that log will tell me exactly which step to handle next. |
|
Hi!
That worked, I got connected and I verified with a Get-HPEGLDevice
My MFA was not trigger but that might be something else.
/Ulf
|
Hi Ulf,
Thanks for the verbose log, it pinpointed the problem. HPE's sign-in service doesn't classify your account as either federated or local, and the library was defaulting to "federated", which sent it to your corporate identity provider instead of signing you in against your HPE account. That's why you saw the "user does not exist" message despite correct credentials.
I've built a test version with a fix. It's not on the PowerShell Gallery, it installs alongside your current version and doesn't touch it.
Instructions are in HOW-TO-USE.md inside the archive. In short: unblock the zip, extract it, open a new PowerShell 7 window, import the module by full path, then run Connect-HPEGL wi…