nsc auth issue-client-cert issues a client certificate tied to your current
Namespace authentication (the same identity used by nsc login or a
configured token). This is useful for tools and integrations that
authenticate to Namespace over mTLS instead of presenting a bearer token
directly.
By default the command generates a fresh key pair and returns the resulting
certificate. You can instead supply your own PEM-encoded public key with
--public_key_file if you’d rather keep the private key material under your
own control, and use --output_private_key_file / --output_public_key_file
to persist a generated key pair to disk for later reuse.