Loading...
Loading...
On any HPE Compute XD690 system; some Redfish API requests may fail with "invalid session resource" errors, resulting in HTTP 401 Unauthorized or 404 Not Found responses.The Redfish requests may fail with an error similar to the following:Bad request: Invalid session resource (/redfish/v1/SessionService/Sessions/dfc5ec04a9b6d35819b575cafb3cbf45), resulting in HTTP 401 Unauthorized.The Redfish interface is configured with a 30‑second default session timeout. Certain management operations can legitimately take longer than 30 seconds to process.When these longer operations exceed the timeout, the session ends unexpectedly, resulting in a 401 or 404 authentication error.
Any HPE Compute XD690 system.
To prevent this issue, increase the Redfish session timeout to prevent these unintended interruptions, setting the Redfish session timeout to 1800 seconds by performing the following steps:Create a Redfish session (get X-Auth-Token):# POST a session to your BMCcurl-k-s-Dheaders.txt \-H"Content-Type: application/json"\-XPOSThttps://<BMC-IP>/redfish/v1/SessionService/Sessions \-d '{"UserName":"<user>","Password":"<pass>"}'# Extract token from response headersgrep-iX-Auth-Tokenheaders.txtPATCH the timeout to 1800:curl-k-s \-H"X-Auth-Token: <token>" \-H"Content-Type: application/json" \-XPATCH \-d '{"SessionTimeout":1800}' \https://<BMC-IP>/redfish/v1/SessionServiceVerify:curl-k-s-H"X-Auth-Token: <token>" \https://<BMC-IP>/redfish/v1/SessionService|jq '.SessionTimeout'The Redfish interface is configured with a 30‑second default session timeout.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.