Hi,
pkispawn is indeed different from the old pkicreate/ web UI
configuration that is used in RHCS 8.x.
The old method required you to pkicreate the instance and the go through
the web UI to configure it. pkispawn does creation and configuration
all together in one non-interactive step.
So, what that means is that its super easy to take dogtag for a spin.
Just do as you have done and run pkispawn, answering all of the
questions along the way. You then have a fully functional CA/KRA - with
no further configuration required.
Now, if you want to customize the system certs, you can run pkispawn
with a config file. To see how to do this, type "man pkispawn". This
will provide examples and point you to more detailed man pages.
Ade
On Wed, 2015-01-28 at 15:37 +0100, marcin kowalski wrote:
Hi, i am testing out dogtag and i wanted to setup a simple local ca
to
take it for a spin.
Following the docs, i created a directory server, pkispawn'ed the ca
and kra instances and after importing the certificate into my browser
for administrative access the difficulties started.
Most guides i found refer to different versions of dogtag apparently,
because they show output of pkicreate command which seems no longer to
exist, and then they lead the user to "CA Setup WIzard" page where all
CA configuration happens. I somehow do not get any access to such
page, so probably the procedure is different now.
I cannot find any such option in the web interface, and i am not
exactly sure what am i missing here. It must be something obvious.
Everything was done on current Fedora installation, with no extra
repositories configured.
_______________________________________________
Pki-users mailing list
Pki-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/pki-users