We're having some certificate issues here. I'm told through the management chain that our network/server dudes are chalking this up to an issue with our internal AD domain being used on the Internet by another org and that this may just be something we have to live with. I am not content with that explanation, as it means a lot of manual work to bandaid RADIUS wireless authentication (and a few other things that "just don't work" like people's personal equipment on our wireless and intel vPro technology that takes a ton of manual work) and we have about 8000 clients here enterprise wide.
Thing is, we own an Internet facing top level domain and have some SSLs etc for our HTTPs website and other crap running on some flavors of Linux. We have some internal servers that we'd like to use SSL certs on and are having issues with validity. Is it possible to have a Windows server (2003 r2 or 2008 r2) with an FQDN of "host.internal.com" and get a go daddy certificate with "host.external.com" and assign that? Or would I be able to make the FQDN of that server which is a member of "internal.com" domain have the FQDN of "host.external.com" so that it will pass validity?
I'm not exactly well versed in PKI. I hope my questions make sense...
[link] [2 comments]