OC 200 custom HTTPS certificate for WebGUI not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

OC 200 custom HTTPS certificate for WebGUI not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OC 200 custom HTTPS certificate for WebGUI not working
OC 200 custom HTTPS certificate for WebGUI not working
2020-08-30 10:44:58
Model: OC200  
Hardware Version: V1
Firmware Version: 1.7.0 Build 20200703 Rel.59609

Hi,

 

I've upgraded recently to the latest firmware (1.7.0) and Controller version 4.1.5.

 

I discovered the option to import certificate + key for the https connection to avoid certificate issues.

 

Basically I requested the cert+key (P12) from the internal certificate authority and converted them to an Java Keystore (JKS).

Import was successfull but even after reboot the certificate is not used, any idea how to analyse the issue more in detail?

Was anybody successfull?

 

 

Any tip highly appreciated. Thanks

  0      
  0      
#1
Options
5 Reply
Re:OC 200 custom HTTPS certificate for WebGUI not working
2020-08-30 13:35:33 - last edited 2020-08-30 13:40:48

@JTJames,

 

it should work principially, see this thread.

 

Maybe your browser has cached the certificate, so try to clear the cache.

Also ensure to use the correct common name (CN) when accessing the web UI.

 

However, JKS format is deprecated since long time. The default format for the Java keystore now is PKCS12. I use PKCS12 format since Omada Software Controller v2.7 and it works also in Omada SDN Software Controller v4.1.5, but unfortunately can't be uploaded to an OC200.

 

I did report this bug to TP-Link already and was informed that it will be fixed in a future firmware version for OC200.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:OC 200 custom HTTPS certificate for WebGUI not working
2020-08-30 15:18:42

@R1D2 

 

Thanks for you answer. I looked into it.

 

I tried several ways, but evertime the same, the Webserver in Omada does not respond with the custom certificate.

 

I created the JKS file it with OpenSSL and the Keystore Explorer, both time same result.

Upload etc. ok but the certificate is not used.

 

Any idea? May an naming issue?

I'm using the hardware version.

 

br

  0  
  0  
#3
Options
Re:OC 200 custom HTTPS certificate for WebGUI not working
2020-08-30 15:57:12

@JTJames, sorry, no more ideas. I didn't verify it with OC200, only SW controller.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:OC 200 custom HTTPS certificate for WebGUI not working
2020-08-30 17:37:16

@R1D2 

 

Hi, ok thanks. I think its definite a bug. I've double checked with the Download version of the controller software which content must be withtin the keystore.

Everything should be ok but even though it does not work, I'll file a ticket.

 

br

  0  
  0  
#5
Options
Re:OC 200 custom HTTPS certificate for WebGUI not working
2020-09-20 15:31:11

Hi all, short update. I'm in contact with the support, until now no solution.

 

br

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 867

Replies: 5

Related Articles