CERTMONGER(1)

✨ getcert — CERTMONGER(1) ✨

okay bestie, welcome to the certmonger manual — this is getcert's page from the General Commands Manual, and it's lowkey iconic 💅

---

💖 NAME 💖

getcert

---

🌸 SYNOPSIS 🌸

getcert resubmit [options]

---

🦋 DESCRIPTION 🦋

So basically? It tells certmonger to generate (or regenerate) a signing request, and then submit (or resubmit) that signing request to a CA so the CA can sign it. That's the whole vibe. ✨

---

🎀 SPECIFYING REQUESTS BY NICKNAME 🎀

• -i NAME, --id=NAME — resubmit a signing request for the tracking request that has this nickname. Now here's the tea: if you don't pass this option, and a tracking entry already exists that matches the key and certificate storage options you specified, then that entry gets used instead. And if you don't specify it and there's no match? Then you gotta say where the certificate lives — either with a combo of the -d and -n options, or with the -f option. periodt.

---

🌈 SPECIFYING REQUESTS BY CERTIFICATE LOCATION 🌈

• -d DIR, --dbdir=DIR — the certificate is chillin' in the NSS database in the directory you name. 💾
• -n NAME, --nickname=NAME — the certificate in the NSS database named with -d has this nickname. Only valid with -d, no cap.
• -t TOKEN, --token=TOKEN — if the NSS database has more than one token available, the certificate is stored in this token. ngl you'll only rarely need to specify this one. Only valid with -d.
• -f FILE, --certfile=FILE — the certificate is stored in the named file. simple as that. 🍓

---

👑 ENROLLMENT OPTIONS 👑

• -c NAME, --ca=NAME — submit the new signing request to the specified CA instead of the one that was previously associated with this certificate. The CA's name should correspond to one listed by getcert list-cas. slay.
• -T NAME, --profile=NAME — request a certificate using the named profile, template, or certtype, from the specified CA.
• --ms-template-spec SPEC — include a V2 Certificate Template extension in the signing request. This datum includes an Object Identifier, a major version number (positive integer), and an optional minor version number. The format is: <oid>:<majorVersion>[:<minorVersion>].
• -X NAME, --issuer=NAME — request a certificate using the named issuer from the specified CA.
• -I NAME, --id=NAME — assign the specified nickname to this task, replacing the previous nickname. glow-up for your task's name 💅

---

🔥 SIGNING REQUEST OPTIONS 🔥

• -N NAME, --subject-name=NAME — change the subject name to include in the signing request.
• -u keyUsage, --key-usage=keyUsage — add an extensionRequest for the specified keyUsage to the signing request. The keyUsage value is expected to be one of these names:
  • digitalSignature
  • nonRepudiation
  • keyEncipherment
  • dataEncipherment
  • keyAgreement
  • keyCertSign
  • cRLSign
  • encipherOnly
  • decipherOnly
• -U EKU, --extended-key-usage=EKU — change the extendedKeyUsage value specified in an extendedKeyUsage extension part of the extensionRequest attribute in the signing request. The EKU value is expected to be an object identifier (OID).
• -K NAME, --principal=NAME — change the Kerberos principal name specified as part of a subjectAltName extension part of the extensionRequest attribute in the signing request.
• -E EMAIL, --email=EMAIL — change the email address specified as part of a subjectAltName extension part of the extensionRequest attribute in the signing request.
• -D DNSNAME, --dns=DNSNAME — change the DNS name specified as part of a subjectAltName extension part of the extensionRequest attribute in the signing request.
• -A ADDRESS, --ip-address=ADDRESS — change the IP address specified as part of a subjectAltName extension part of the extensionRequest attribute in the signing request.
• -l FILE, --challenge-password-file=FILE — add an optional ChallengePassword value, read from the file, to the signing request. A ChallengePassword is often required when the CA is accessed using SCEP.
• -L PIN, --challenge-password=PIN — add the argument value to the signing request as a ChallengePassword attribute. A ChallengePassword is often required when the CA is accessed using SCEP.

---

💜 OTHER OPTIONS 💜

• -B COMMAND, --before-command=COMMAND — whenever the certificate or the CA's certificates are saved to the specified locations, run the specified command as the client user before saving the certificates.
• -C COMMAND, --after-command=COMMAND — whenever the certificate or the CA's certificates are saved to the specified locations, run the specified command as the client user after saving the certificates.
• -a DIR, --ca-dbdir=DIR — whenever the certificate is saved to the specified location, if root certificates for the CA are available, save them to the specified NSS database.
• -F FILE, --ca-file=FILE — whenever the certificate is saved to the specified location, if root certificates for the CA are available, and when the local copies of the CA's root certificates are updated, save them to the specified file.
• --for-ca — request a CA certificate.
• --not-for-ca — request a non-CA certificate (the default).
• --ca-path-length=LENGTH — path length for CA certificate. Only valid with --for-ca.
• -w, --wait — wait for the certificate to be reissued and saved, or for the attempt to obtain one to fail. patience is a virtue bestie 😭
• --wait-timeout=TIMEOUT — maximum time to wait for the certificate to be issued.
• -v, --verbose — be verbose about errors. Normally, the details of an error received from the daemon will be suppressed if the client can make a diagnostic suggestion. (basically: it shuts up when it thinks it knows what's wrong, unless you pass this. 🙈)
• -o OWNER, --key-owner=OWNER — after generation, set the owner on the private key file or database to OWNER.
• -m MODE, --key-perms=MODE — after generation, set the file permissions on the private key file or database to MODE.
• -O OWNER, --cert-owner=OWNER — after generation, set the owner on the certificate file or database to OWNER.
• -M MODE, --cert-perms=MODE — after generation, set the file permissions on the certificate file or database to MODE.

---

💀 BUGS 💀

Please file tickets for any that you find at https://fedorahosted.org/certmonger/

(not me asking you to snitch on the bugs, but like, do it, they wanna know 🫶)

---

⭐ SEE ALSO ⭐

certmonger(8) getcert(1) getcert-add-ca(1) getcert-add-scep-ca(1) getcert-list-cas(1) getcert-list(1) getcert-modify-ca(1) getcert-refresh-ca(1) getcert-refresh(1) getcert-rekey(1) getcert-remove-ca(1) getcert-request(1) getcert-start-tracking(1) getcert-status(1) getcert-stop-tracking(1) certmonger-certmaster-submit(8) certmonger-dogtag-ipa-renew-agent-submit(8) certmonger-dogtag-submit(8) certmonger-ipa-submit(8) certmonger-local-submit(8) certmonger-scep-submit(8) certmonger_selinux(8)

---

okay that's the whole page, you ate that reading it 💅 this was the certmonger Manual, dated February 9, 2015 — and that's on periodt, bestie. go forth and resubmit those signing requests, no cap 🌸🦋✨