This project is originally designed for Kener to support Windows CA monitoring and report its status to the API using a Powershell script.
All the parameters were designed just like the way it shows in pkiview.msc to act as an alternative.
Actually you can use any Status Page Service because it just use Invoke-WebRequest to send status to APIs...
- A Functioning Windows Server CA (You can use
pkiview.mscto view that) - A Client installed with Powershell v5 or later to host the script (Better on Windows 7 & Server 2008 R2 and later versions)
- A Path to put all the CRL&Certificates temporarily
- A Computer with OpenSSL installed (Only for OCSP Support)
- If you're only using Windows and don't use Linux or Unix based systems, you can download OpenSSL here
- Use
pkiview.mscto check your CA is functioning - Write down all the information in
pkiview.msc - Change the variables according to your environment (Using the information from the above step)
- Generate a request body for OCSP testing using OpenSSL (Listed Below)
- Get your CA certificate and a certificate which was revoked
- Put all the Files under the same path with the script
- Test the script before production
- Set the script to run every x minute as you like (Use Scheduled Tasks Manager shipped with Windows)
- Done!
- Create an OCSP request to work with, this also will produce a POST to the OCSP responder
openssl ocsp -noverify -no_nonce -respout OCSP.resp -reqout OCSP.req -issuer CA.cer -cert Revoked.cer -url "your_ocsp_address" -header "HOST" "your_ocsp_host" -text - Put the
OCSP.reqfile under the same path with the script
- Huge thanks for UNMITIGATED RISK providing the method to generate ocsp request body!
- Thanks Kener for Status Pages and the idea!