You really shouldn't mix/combine the security of completely different services (thats what a certificate is - service identity) in a single certificate. The proper solution is to up the automation surrounding your service's build process to include the asynchronous process of obtaining a certificate for each service.
If you need multiple hostnames for the same certificate (AND KEYPAIR), you should be using SAN certificates, not wildcards.
If you need multiple endpoints with the same DNS hostname, you make that a common SAN across multiple certs for each individual TLS endpoint.
As a follow-up, IMO, the only valid use case for wild card certs is for self-contained private PKIs usedd internally with external certs for the exposed service endpoints. An example would be a private mini-CA dedicated (and trusted) only for inter-node internal connections within the cluster.
Thank you for your description and follow-up.
I'm so grateful to you 🙂
I'll learn and get experienced much more...
Do you have a reference source link for your statement: "You really shouldn't mix/combine the security of completely different services (thats what a certificate is - service identity) in a single certificate."
In a blog post of mine I want to link to your comment here but, also link to an official document/RFC.
Thanks a lot - and thanks heddi.nabbisen for this post!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.