Root certificate in switch HP V1910-48G Switch JE009A

[Dmitry---spb]

Hi all, sorry for my english))

Problem: I have a domain Windows 2008r2 with a PKI infrastructure, try to load the root certificate to the switch, and I get the error: CA root certificate is not trusted. Сertificate is signed with a SHA512 hash. Any ideas?

P.S. This thread has been moved from Switching > Switches, Hubs, Modems (Legacy ITRC forum) > to Web and Unmanaged.-HP Forum Moderator

[rorosit]

altough this post is from 2013, we encountered this problem too, yesterday (2017) ;)

our root CA is sha512 and 4096bits. the switch refuses to import the root ca cert.

we then installed a lab CA with sha1 and 2048bits root cert. this cert imports fine.

seems like the hp firmware doesn't like the stronger encryption. in 2013... ok.... but in 2017 ?? come on.

model: HPE 1910-8G Switch JG348A

firmware: 5.20 Release 1519P01

[LuukDost]

Can you please explain to me where you can import this Root Certificate and how? I'm breaking my head on this one. On the following page I've made a tuturial of what we try to do on our HPE 1910-8G-PoE+ (180W) Switch JG350A and what errors I'm getting. 

I would very much appreciate it if you could help me out here.

[LuukDost]

https://community.hpe.com/t5/Web-and-Unmanaged/Cannot-configure-Custom-Certificate-on-HP-Switch-1910/td-p/6989347

[Lloyd_mcse]

Yup, same issue here using the latest firmware available for the HPE 1920-8G, I'm using an ECC Root CA (ECC 256 with SHA256).

I originally thought it was because the whole certificate was ECC, so I created a RSA one and still the same, it appears it doesn't like our Root CA.

The really annoying thing is our HP ENVY Printer had no problem with the RSA certificate I generated for it! 

[zsing82]

Been working through this issue myself recently.  Got a 1910-8G running 5.20 Release 1519P03 and started having this problem when I needed to renew my web server cert for the switches admin page.  The only thing I found to work was to disable CA verification by deleting the fingerprint information in PKI Domain.  Not ideal, but works.  Hope it helps.