Dell iDRAC

Storage and virtualisation

Renews the iDRAC HTTPS certificate using the method advertised by its firmware and checks the served identity.

What happens

The appliance connects to Dell iDRAC through iDRAC HTTPS API on port 443.
Discovery reads firmware, served certificate, certificate actions and SCEP/ACME/ACE enrollment. The package retains identity and enrollment before changing them.
CustomCertificate uses PKCS12; HTTPS ReplaceCertificate uses PEM with the firmware’s URI. Older devices use remote RACADM and may require a controller restart; the host is never rebooted. If it fails: Recovery after failure needs the matching previous key. Without it a failed split key/certificate upload can require manual recovery.
Verification requires the new served leaf and intermediate chain. Rollback restores the previous leaf, key, chain and enrollment from the private backup and checks the identity again.

Connection: The package runs on the appliance, which connects over HTTPS to iDRAC HTTPS API, port 443. No agent is installed.
Service ports: 443
You need: An iDRAC account permitted to use the discovered import method and enrollment settings. Older generations require Dell remote RACADM on the relay.
Platform: Dell iDRAC 8, 9 and 10
Actions: Discovery, Installation, Verification, Rollback
Packages: dell-idrac-api
Note: First installation can proceed without the previous key. A public certificate export is not a key backup. Previous key material comes from a retained deployment, matching issuance key, supported private export or PREVIOUS_KEY_PEM_BASE64.
Only the HTTPS identity and its enrollment are changed. CA and hostname verification are the default; select MANAGEMENT_TLS_PIN_SHA256 or a CA bundle when needed. Retain the private backup for later rollback.