OC200 SSL Certificates and Hostname

OC200 SSL Certificates and Hostname

OC200 SSL Certificates and Hostname
OC200 SSL Certificates and Hostname
2 weeks ago - last edited 2 weeks ago
Model: OC200  
Hardware Version: V1
Firmware Version: Hardware V 1.6; on Firmware OC200(UN)_V1_1.31.3 Build 20240620

Good day. 

 

We are moving toward having valid SSL certs for all devices in our envirnment and are having a problem getting our internally generated certificate for the OC200 to be presented.  From this post: https://community.tp-link.com/en/business/forum/topic/207630? we can see that progress has been made in this area and that is appreciated.  Our OC200 has a hostname specified which has only lowercase alpha and some numbers, no underscores or hyphens or other special characters.  We have successfully created and uploaded a certificate and private key to the OC200 in PEM format and those files have been successfully saved to the OC200.

 

However, when connecting to the OC200, it still delivers a certificate with the following characteristics:

  Issued To

    Common Name (CN)            localhost

    Organization (O)                   TP-Link

    Organizational Unit (OU)      TP-Link

  Issued By

    Common Name (CN)            localhost

    Organization (O)                   TP-Link

    Organizational Unit (OU)      TP-Link

  Validity Period

    Issued On      Tuesday, December 6, 2022 at 2:00:04 AM

    Expires On     Monday, March 10, 2025 at 3:00:04 AM

 

Is there anything else required for the OC200 to acually use / present the SSL certificate which we uploaded?

 

Thanks for your help.

 

Best,

Carl

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:OC200 SSL Certificates and Hostname-Solution
2 weeks ago - last edited 2 weeks ago

  @clangren 

 

Almost deleted this and then thought better of it.....

 

Second reboot and all is well. Had to be something I did wrong....

 

 

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:OC200 SSL Certificates and Hostname-Solution
2 weeks ago - last edited 2 weeks ago

  @clangren 

 

Almost deleted this and then thought better of it.....

 

Second reboot and all is well. Had to be something I did wrong....

 

 

Recommended Solution
  0  
  0  
#2
Options

Information

Helpful: 0

Views: 74

Replies: 1

Related Articles