> ## Documentation Index
> Fetch the complete documentation index at: https://namespace.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# nsc auth issue-client-cert

Issue a client certificate for the current Namespace authentication token.

`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.

## Usage

```bash theme={null}
nsc auth issue-client-cert [--output_private_key_file string] [--output_public_key_file string] [--public_key_file string]
```

### Example

```bash theme={null}
nsc auth issue-client-cert \
  --output_private_key_file client.key \
  --output_public_key_file client.pub
```

## Options

<h3 id="--output_private_key_file-string">
  \--output\_private\_key\_file string
</h3>

If specified, write the generated private key PEM to this path.

<h3 id="--output_public_key_file-string">
  \--output\_public\_key\_file string
</h3>

If specified, write the generated public key PEM to this path.

<h3 id="--public_key_file-string">
  \--public\_key\_file string
</h3>

If specified, use this PEM-encoded public key instead of generating one.