Thanks Niranjan, I submitted 'Manual User Dual-Use Certificate Enrollment¹ via End User interface and got it approved via agent interface and imported it to browser including the keys. My confusion is where the keys (private key) came from? Was it automatically generated when I submitted the Certificate Enrollment request via browser? Or was it created by the Dogtag server and delivered it to browser when I imported the cert? Thanks in advance. Mahendra On 3/30/15, 12:24 PM, "Niranjan M.R" <mrniranjan@redhat.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/30/2015 09:16 PM, Jain, Mahendra wrote:
Hello All,
When I install the Dogtag Certificate System, the installation creates default PKI Administrator user (caadmin). What is the procedure to setup additional PKI Administrator users so that they can also access agent interface? If you are on latest dogtag (fedora 20), you could pki user cli to create user and add him to Certificate Manager Agents Group . Also use a user profile to generate cert for the new user and add the cert using pki user cli . Import the cert to browser (including keys).
You could do the same using pkiconsole too.
Thanks, Mahendra
³This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.²
_______________________________________________ Pki-users mailing list Pki-users@redhat.com https://www.redhat.com/mailman/listinfo/pki-users
- -- Niranjan irc: mrniranjan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iKYEARECAGYFAlUZeMRfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldEY3OTE3QTg3ODE0RkVCQ0YyNjgyOTRENjJF RURDNTVGNjA0N0M3QzcACgkQLu3FX2BHx8dsCwCgh14OK+0ZFyFYUWkEt04Idgq0 E4kAoIohPEYgdwXYLXPiMunLSyDhEOQz =766t -----END PGP SIGNATURE-----