Hi Scott,
Sitenote/Bug Report for OpenXPKI:
Currently the CRL configuration of profile.xml doesn't provide
validity dates less than 1 day. For example 12 hours don't work:
<!-- <notafter format="relativedate">+00000012</notafter> -->
Scott writes:
> how can i integrate the "OpenCA Responder" with "OpenXPKI".
1st step:
Your OpenXPKI environment should be able to generate a CRL,
here's an example for a CRL configuration which is valid 14 days
("000014" is for 00 years, 00 months, 14 days),
I've equipped my two profile id's "rootCA" and "SubCA" with this
default profile credentials in my example:
/etc/openxpki/profile.xml:
<profiles id="default_profiles">
<crl>
<profile id="default">
<validity>
<!-- notbefore is not applicable here -->
<notafter format="relativedate">+000014</notafter>
</validity>
<digest>sha1</digest>
<extensions>
</extensions>
</profile>
<profile id="rootCA"
super="../profile{default}"/>
<profile id="SubCA"
super="../profile{default}"/>
</crl>
2nd step:
You should setup a cron job which generates a new CRL once a day --
or let's say each half an hour, but currently the OpenXPKI database
fills up with each generated CRL (within the "workflow" table),
so your database could blow up a bit. You could use openxpkicmd
for this.
3rd step:
Set-up OpenCA-OCSPD within ocspd.conf:
First, i set the CRL reload time very low. This means OCSPD
looks every minute (= 60 seconds) whether OpenXPKI has generated
a new crl file:
crl_auto_reload = 60
Then you configure in the dbms_file section the actual file locations:
[ dbms_file ]
0.ca = @first_ca
1.ca = @second_ca
[ first_ca ]
crl_url = file:////etc/ssl/rootCA/crl/crl.pem
ca_url = file:////etc/ssl/rootCA/certs/cacert.pem
[ second_ca ]
crl_url = file:////etc/ssl/SubCA/crl/crl.pem
ca_url = file:////etc/ssl/SubCA/certs/cacert.pem
I've read on the OpenCA-OCSPD mailinglist that OCSP-Daemon
would produce invalid response signatures after running for a while,
so you should restart OCSP daemon frequently, or - as a workaround
- you could also use another, compatible application: OpenSSL.
As a prerequirement you would have to export all certificates
from OpenXPKI into OpenSSL compatible filespace, generate an
appropriate "index.txt" to it (it'd be nice, if OpenXPKI would
have such an export script to OpenSSL directory structure anyway).
Then, the function call would be:
openssl ocsp -index index.txt -port 8080 \
-rsigner cacert.pem -CA cacert.pem -rkey cakey.pem -text
Unfortunately "openssl ocsp" doesn't seem to work together with all HSMs.
Greetings
-Achim
--
Joachim Astel | [email protected] | OpenXPKI + OpenCA-OCSPD + OpenCA-Tools
------------------------------------------------------------------------------
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users