问题原文
原帖链接 · tk-noodle · CC BY-SA 4.0
My org deploys a data server and a client device (two devices) in customers' internal networks for them to use our solution; the client device only connects to the data server; however any one customer site may not necessarily provide a static IP or a hostname, nor guarantee the persistence of the devices' IPs. The only things we know for sure we can control are our server and the client device; customers' requirements dictate the network setup.
The client device needs to connect securely to the data server over HTTPS, and we want to provide the option of installing our own certificate using our own CA on the data server. (of the customer can also install their own certificate, but that's beyond the scope of this question)
Since the data server's IP is not guaranteed persistence, I am left wondering, is it possible to issue a certificate to a service, rather than issuing the certificate for the address/name?
I've looked for "ssl certificates for services" and "for variable IPs" and suchlike, but found nothing relevant. Am I missing some terminology to help narrow down my search, or is this just not a thing at all?
Thanks
已采纳解答
原帖链接 · Gerald Schneider · CC BY-SA 4.0
Ship a self signed certificate and provide a possibility for the customer to upload their own certificate.
That's how everybody does it, because it's the only option that really works. An administrator who sets up a service expects this, and has the option to install a valid certificate for his users.
After reading the question again and thinking about it, I think there actually is an option:
for the user interface:
- ship with self signed certificate
- provide option to upload a certificate for admins
for the inter-device communication:
- create your own CA (in your own internal network, this CA does not leave your company)
- configure the client devices you ship to your customers to trust this CA
- create a Sub-CA of your CA on your server device
- after installation of the server at the customer site have the server device create a certificate for itself by the sub-ca
- at this point you have the IP address and can resolve the IP address to an valid internal DNS name
- (optional: after installation of the client at the customer site have the client device request a certificate from the sub-ca on the server.
This isn't really necessary, but it could be used to have the server authenticate the client, if you only want your own clients to be able to communicate with the server)
This way your clients trust your own server, and you can even extend it to a two-way trust between your devices alone.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
