M283cdw EWS bug: changing Configuration Precedence reverts custom HTTPS certificate

[twodollars]

Product: HP Color LaserJet Pro MFP M283cdw

Problem: Changing the EWS Network Identification > Configuration Precedence setting causes the printer to stop using an installed custom HTTPS printer certificate and revert to the factory HP self-signed certificate.

I am using a valid CA-signed printer certificate installed through the printer's Embedded Web Server (EWS). The certificate works correctly for HTTPS access and is presented correctly by the printer on TCP port 443.

Steps to reproduce:

1. Install a custom CA-signed printer certificate under Networking > Certificates.
2. Verify that the printer presents the custom certificate when accessing the EWS over HTTPS.
3. Go to Networking > Network Identification.
4. Change Configuration Precedence. In my case I changed the order from:
   Manual > TFTP > DHCP/BootP > DHCPv6 > Default
   to:
   DHCP/BootP > Manual > TFTP > DHCPv6 > Default
5. Apply the change. The printer reboots.
6. After the reboot, access the EWS over HTTPS and inspect the printer certificate.

Actual result:

The previously installed custom certificate is no longer being used. The printer instead presents its factory HP self-signed certificate, with the factory/default NPI hostname as the certificate subject.

Changing Configuration Precedence back to the original factory order and rebooting does not restore the custom certificate. The custom certificate must be imported again.

After re-importing the same custom certificate, the printer again presents it correctly over HTTPS. I verified the certificate actually served on TCP port 443 using OpenSSL, including its issuer, subject, validity period, and Subject Alternative Names.

Expected result:

Changing the Configuration Precedence order should affect only the precedence of network configuration sources such as DHCP/BOOTP, Manual, TFTP, DHCPv6, and Default. It should not remove, deactivate, or replace an independently installed HTTPS printer certificate.

Additional observation:

The HP certificate that becomes active after this change is not newly generated at the time of the configuration change. Its issue date predates the test, which suggests the printer is reverting to or reactivating an existing factory self-signed certificate.

This behavior is reproducible and appears to be an EWS/firmware defect. I would appreciate this being escalated to the LaserJet firmware/EWS engineering team for investigation.