CERTMONGER(1)
π CERTMONGER π
okay bestie, pull up a chair, we're talking about ipa-getcert β it lives in the General Commands Manual section and it's lowkey one of the most useful little tools in the whole certmonger fam. β¨
πΈ NAME πΈ
ipa-getcert β your girl for asking certmonger to do cert things on your behalf π
β¨ SYNOPSIS β¨
ipa-getcert request [options]
ipa-getcert resubmit [options]
ipa-getcert start-tracking [options]
ipa-getcert status [options]
ipa-getcert stop-tracking [options]
ipa-getcert list [options]
ipa-getcert list-cas [options]
ipa-getcert refresh-cas [options]
π¦ DESCRIPTION π¦
So here's the vibe: the ipa-getcert tool issues requests to a org.fedorahosted.certmonger service on behalf of the invoking user. Not on behalf of some rando β on behalf of you, the one who ran the command. π
It can do a whole little list of things for you:
- ask the service to begin enrollment, and optionally generate a key pair to use while it's at it π
- ask the service to begin monitoring a certificate in a specified location for expiration, and optionally refresh it when expiration nears π
- list the set of certificates that the service is already monitoring
- list the set of CAs that the service is capable of using
If no command is given as the first command-line argument, ipa-getcert will print short usage information for each of its functions. (Translation: you get the menu, not the meal. π½οΈ)
Here's the tea though β the ipa-getcert tool behaves identically to the generic getcert tool when it is used with the -c IPA option. Same energy, different name, fr fr. π«Ά
Also, certmonger supports retrieving trusted certificates from IPA CAs. So if you wanna know how to use the -F and -a options to specify where those certificates should be stored, go read getcert-request(1) and getcert-resubmit(1). iykyk β¨
π BUGS π
Found a bug? Please file tickets for any that you find at
https://fedorahosted.org/certmonger/
no cap, they wanna hear about it π
π SEE ALSO π
the whole friend group, in order:
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-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, bestie!! this one's from the certmonger Manual, dated November 3, 2009, and it's page CERTMONGER(1) in the manual set. iconic behavior tbh, go get those certs πβ¨
π¦ where this page comes from
- alpine 3.24: certmonger-doc 0.79.21-r0 Β· GPL-3.0-or-later
- centos-stream 10: certmonger 0.79.21-1.el10 Β· GPL-3.0-or-later
- centos-stream 9: certmonger 0.79.21-1.el9 Β· GPLv3+
- debian bookworm: certmonger 0.79.17-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- debian trixie: certmonger 0.79.20-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- fedora 43: certmonger 0.79.20-5.fc43 Β· GPL-3.0-or-later
- fedora 43: certmonger 0.79.21-1.fc43 Β· GPL-3.0-or-later
- fedora 44: certmonger 0.79.21-4.fc44 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- ubuntu jammy: certmonger 0.79.14+git20211010-2ubuntu1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu noble: certmonger 0.79.19-1build4 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu questing: certmonger 0.79.20-2build1
- ubuntu resolute: certmonger 0.79.21-1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu stonking: certmonger 0.79.21-1build1 Β· GPL-3.0-or-later WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms