Conversation
miharp
force-pushed
the
docs/ca-cli-auth
branch
from
September 15, 2026 12:00
39a7fad to
5a8cf20
Compare
miharp
marked this pull request as ready for review
September 15, 2026 13:06
bastelfreak
reviewed
Sep 15, 2026
| } | ||
| ``` | ||
|
|
||
| See [CA CLI authorization](./subcommands.html#ca-cli-authorization) for how the server's own certificate gets that extension and how to issue it to another host. |
Contributor
There was a problem hiding this comment.
I don't know if we need to make this distinction: We can create unlimited certificates with this certificate extension and IMO it's common to have multiple of them - if you need to call the APIs from other services.
Contributor
Author
There was a problem hiding this comment.
makes sense, updated it.
…ments Explain that puppetserver ca setup and ca import stamp the server's own certificate with the pp_cli_auth extension, that the default auth.conf authorizes the CA administrative endpoints on that extension rather than by certname, and that --ca-client is the way to issue it to another host. Add pp_owner, pp_auth_auto_renew, and pp_cli_auth to the registered OIDs table and give the ppAuthCertExt rows a proper table header. Correct the certificate status page, which still said the endpoint was disabled by default, and the bulk sign page, which pointed at ca.conf instead of auth.conf. Replace the Puppet 5 upgrade note on the subcommands page with a CA CLI authorization section and show the shipped cert status rule as the extensions example on the auth.conf page. Closes OpenVoxProject#484 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Michael Harp <mike@mikeharp.com>
Review feedback: the server's own certificate is not special. Any service that calls the CA API gets a certificate with the extension, and having several is normal, so stop framing the server as the holder and other hosts as the exception. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Michael Harp <mike@mikeharp.com>
miharp
force-pushed
the
docs/ca-cli-auth
branch
from
September 18, 2026 10:57
a89712d to
5563809
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #484
A recent Slack thread had maintainers unsure why
puppetserver ca listworks on a fresh primary with no auth.conf changes. The answer (the server's own certificate carries thepp_cli_authextension, and the shippedauth.confauthorizes the CA admin endpoints on that extension) was not written down anywhere, and a few related pages still carried statements from before that mechanism existed.Changes, applied to both the 8.x and 9.x trees:
allow: master.example.comexample with a "CA CLI authorization" section. It explains thatca setupandca importaddpp_cli_authto the server certificate, how to check for it withopenssl x509, what breaks if the server certificate is regenerated another way, and thatpuppetserver ca generate --ca-clientis the supported way to issue the extension to another host (with a warning that it is an administrative credential).puppetlabs cert statusrule as the worked example ofextensionsmatching and link to the new section.pp_owner,pp_auth_auto_renew, andpp_cli_auth, whichlib/puppet/ssl/oids.rbregisters but the table omitted. The ppAuthCertExt rows had no table header, so they rendered as a paragraph; this adds one.auth.conf, notca.conf.Sources:
openvoxserver-cagemlocal_certificate_authority.rb(CLI_AUTH_EXT_OID,add_authorized_extensions, called fromsetup.rb,import.rb, and the--ca-clientpath ingenerate.rb) and openvox-serverezbake/config/conf.d/auth.conf.Verified with
markdownlint-cli2on every touched file and a fulljekyll build; the new anchor resolves from all four linking pages in both trees.Assisted by Claude.