Hello
Can someone please help me with the following question.
Here is the background.
We have one Active Directory Domain with an AD CS Enterprise CA (domain joined), in this domain we have the usual Windows computers, users, groups etc.
We also have a 'separate' Linux/Unix environment which has its own 'Kerberos realm' (no trust between this realm and our AD Kerberos realm)
We want to issue certificate 'automatically' to our Linux/Unix clients from our AD CS. We realise there are a number of comcercial solutions available but we are not looking at this right now.
The UNIX guys can setup a SCEP Server (Proxy), this SCEP Server uses Kerberos to authenticate the Linux client requesting a certificate via this SCEP proxy (to check they are allowed to request a certificate via SCEP or not)
The problem is interfacing this UNIX SCEP proxy to AD as a trusted RA (registration authority), more over the SCEP Server would need to issue DCOM requests to the CA (to request and retrieve certificates for example, we are not looking at using certificate
enrolment policy/web services)
Therefore we was thinking about trying the following configuration and my question is, is the following a possible/plursiable configuration (as I have not setup NDES before).
Set and NDES Server to service SCEP requests to/from the AC CS (in the usual way up to now).
However rather than letting 'any' SCEP client to request certificates from the NDES Server; lock it down so only the UNIX SCEP proxy can proxy SCEP requests via the NDES Server.
With the above configuration I was thinking of possibly using https or IPsec to secure the communication between the UNIX SCEP proxy and the NDES Server in such a way that no other host can talk/make SCEP requests for certs to the NDES Server.
But then I am thinking what about the SCEP challenge the Linux client needs to present to the NDES Server (I have not setup NDES before and understand NDES by default issues and expects back a SCEP challenge),
Can I turn this SCEP challenge off completely. The reason I want to turn off the SCEP challenge is to make the automation of issuing certificates to these Linux clients easier and these Linux clients have already been 'authenticated' (via
their own Kerberos realm). Although the AD domain does not have trust setup with the Unix Kerberos realm we trust in, therefore happy to setup an IPsec or https tunnel to it to proxy the requests through.
Any advice/help would be most welcome
Thanks all
Ernie