Hey Martin, I will try it out so that it then accesses the database. I already had a post where it is for me when I create a web server certificate with advanced configuration that it adds spaces to me, for example "test .key". If I do with default configuration there is no space but I can't assign an IP. Can I insert IP line somehow with default configuration?
Martin Bartosch via OpenXPKI-users <openxpki-users@lists.sourceforge.net> schrieb am Mi. 14. Aug. 2024 um 12:20: > Hi, > > > Can someone help me or tell me which OCSP I can take. I read that one of > EJBCA took it. > > You can use any OCSP responder that either reads a standard CRL or > accesses the OpenXPKI database. > > Personally I tried the EJBCA OCSP responder some time ago and I am not too > fond of it. It's a huge, sluggish and resource-hungry beast. > > For OpenXPKI Enterprise Edition we offer an extremely efficient and > blazingly fast OCSP responder that accesses the OpenXPKI database and which > also can be easily operated distributed. However, this is not available for > the Community Edition. > > > Does anyone have an idea? And what is the easiest way to get the CRL > list exported without accessing the WebGui. > > Configure the CRL publishing connector as required. The default > configuration already writes the CRL to the file system, so you can simply > use that. Automate CRL issuance by invoking the crl_issuance workflow for > the desired realm via > > openxpkicmd crl_issuance --realm REALM > > Cheers > > Martin > > > > _______________________________________________ > OpenXPKI-users mailing list > OpenXPKI-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openxpki-users >
_______________________________________________ OpenXPKI-users mailing list OpenXPKI-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openxpki-users
