FLPeople We are doing some internal testing using a web application hosted in IIS and using SSL security (On
Windows 2003 Server). We currently have a test web site that is using an internally created certificate (created from our internal CA structure) to SSL (https) the web page.
First a look at our internal CA structure. The Root CA is in our Root Domain (ourname.net) of our domain structure. 2 Subordinate CA’s are in the Sub-Domain (office.ourname.net) of our domain structure.
The web server and clients exists in office.ourname.net domain – shown below.
We did some network traffic monitoring while testing client access to the secured website. When the client’s browser setting for “check for server certificate revocation” is turned on. – we were surprised to see traffic from our clients not only to the Subordinate CA (we expected this), but also to the Root CA. We are assuming this was to check for a recent CRL (certificate revocation list) to make sure the given certificate has not since been revoked from its original creation.
Given that we plan to take our Root CA offline in the near future – this is concerning.
1. Why would this be happening if the subordinate was the CA that issued the cert to the web server?
2. Was there an error in the way we created this certificate for the website?
3. Is there an error in the way we are handling CRL’s in relation to our Root CA?
4. How can we offline our Root CA if it is actively publishing CRL’s - and apparently from this test - our clients will be looking from them.
(I know its 4 questions here - will split points if need be)
gheist
If you take your CRL offline make sure web server is taken off and refuses http connections, so that users feel less timeout.
pcsmitpra
1. Why would this be happening if the subordinate was the CA that issued the cert to the web server?
>>>> Have you placed the ROOT certificate in the place on webserver using certificate wizard ,becoz browser was trying to get root certificate.
2. Was there an error in the way we created this certificate for the website?
>>>> Does not seems though Not sure.
3. Is there an error in the way we are handling CRL’s in relation to our Root CA?
>>>> Please check if CRL on your webserver is updated and not bad. You can find it in certificate wizard.
4. How can we offline our Root CA if it is actively publishing CRL’s - and apparently from this test - our clients will be looking from them.
>>>> If Client gets the GOOD CRL , Root Cert and intermediate cert from Webserver itself it wont try to reach Root server, considering the FQDN is fine and SSL is placed to right domain with correct hostname. Probably you would like to import a latest CRL file from root server to web server.
Windows 2003 Server). We currently have a test web site that is using an internally created certificate (created from our internal CA structure) to SSL (https) the web page.
First a look at our internal CA structure. The Root CA is in our Root Domain (ourname.net) of our domain structure. 2 Subordinate CA’s are in the Sub-Domain (office.ourname.net) of our domain structure.
The web server and clients exists in office.ourname.net domain – shown below.
We did some network traffic monitoring while testing client access to the secured website. When the client’s browser setting for “check for server certificate revocation” is turned on. – we were surprised to see traffic from our clients not only to the Subordinate CA (we expected this), but also to the Root CA. We are assuming this was to check for a recent CRL (certificate revocation list) to make sure the given certificate has not since been revoked from its original creation.
Given that we plan to take our Root CA offline in the near future – this is concerning.
1. Why would this be happening if the subordinate was the CA that issued the cert to the web server?
2. Was there an error in the way we created this certificate for the website?
3. Is there an error in the way we are handling CRL’s in relation to our Root CA?
4. How can we offline our Root CA if it is actively publishing CRL’s - and apparently from this test - our clients will be looking from them.
(I know its 4 questions here - will split points if need be)
gheist
If you take your CRL offline make sure web server is taken off and refuses http connections, so that users feel less timeout.
pcsmitpra
1. Why would this be happening if the subordinate was the CA that issued the cert to the web server?
>>>> Have you placed the ROOT certificate in the place on webserver using certificate wizard ,becoz browser was trying to get root certificate.
2. Was there an error in the way we created this certificate for the website?
>>>> Does not seems though Not sure.
3. Is there an error in the way we are handling CRL’s in relation to our Root CA?
>>>> Please check if CRL on your webserver is updated and not bad. You can find it in certificate wizard.
4. How can we offline our Root CA if it is actively publishing CRL’s - and apparently from this test - our clients will be looking from them.
>>>> If Client gets the GOOD CRL , Root Cert and intermediate cert from Webserver itself it wont try to reach Root server, considering the FQDN is fine and SSL is placed to right domain with correct hostname. Probably you would like to import a latest CRL file from root server to web server.
No comments:
Post a Comment