CERTMONGER(1)

💖 CERTMONGER — the getcert era 💖

okay bestie, sit down, hydrate, because this one's a whole suite. this is the manual page for getcert, from the certmonger package. she's a command-line queen with like fourteen subcommands and she does NOT do anything halfway. let's get into it 🎀

---

✨ NAME ✨

getcert — that's her. that's the name. periodt.

---

🌸 SYNOPSIS 🌸

getcert request [options]
getcert start-tracking [options]
getcert stop-tracking [options]
getcert resubmit [options]
getcert rekey [options]
getcert refresh [options]
getcert list [options]
getcert status [options]
getcert add-ca [options]
getcert add-scep-ca [options]
getcert list-cas [options]
getcert modify-ca [options]
getcert refresh-ca [options]
getcert remove-ca [options]

like… pick a lane, bestie. any lane. there's fourteen of them and they all take [options] 💅

---

🦋 DESCRIPTION 🦋

so here's the vibe: the getcert tool slides into the DMs of a org.fedorahosted.certmonger service on behalf of the user who invoked it. she's not doing the work herself, she's asking the service very nicely. it's giving delegation, it's giving "not my job but i know a girl" 💖

what she can ask the service to do:

• begin enrollment — and optionally generate a key pair to use while she's at it 🔑
• begin monitoring a certificate in a location you specify, to watch for expiration — and optionally refresh it when expiration gets close 👀
• list the set of certificates the service is already monitoring
• list the set of CAs the service is capable of using

and if you run her with no command as the first command-line argument? she'll just print short usage information for each of her functions. she's helpful like that, no cap 🫶

one more thing, and this one's lowkey important: if getcert is invoked by a user with UID 0, and there's no system bus available, she will attempt to launch a temporary copy of the certmonger daemon just to handle her requests. main character energy fr fr 👑

---

💜 COMMON ARGUMENTS 💜

these apply across the board, so pay attention bestie:

• if CERTMONGER_PVT_ADDRESS is set in the environment, getcert contacts the service directly at the specified location. skipping the middleman, iconic 💅
• all commands can take either the -s or the -S arguments — these tell getcert to contact the org.fedorahosted.certmonger service on the session or the system bus, if no value is set.
• by default (no value set), getcert consults the org.fedorahosted.certmonger service attached to the system bus. that's the default, that's the norm, that's just how she rolls ✨

---

🌈 EXIT STATUS 🌈

the exit status is 0 on success, and nonzero on error. dramatic? maybe. accurate? absolutely.

• 0 — Success 🎉
• 1 — Error 😭
• 2 — Duplicate entry 💀

---

🙈 BUGS 🙈

found a bug? please file tickets for any that you find at https://fedorahosted.org/certmonger/ — the maintainers wanna know, fr fr, don't just suffer in silence 🫶

---

👑 SEE ALSO 👑

your reading list, bestie, go off:

• certmonger(8)
• 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-resubmit(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)

---

and that's the whole page, babe 💖

this one's from the certmonger Manual, dated November 3, 2009, and it lives under CERTMONGER(1). vintage but still serving looks, we love to see it ⭐🌸🦋