> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/certificate-management/jamf/computers.md).

# Computers

Deploy SCEPman root and device certificates to macOS computers.

Deploy a device certificate to macOS computers through a Jamf Pro configuration profile. First complete the [General Configuration](https://docs.scepman.com/certificate-management/jamf/general.md).

{% hint style="success" %}
Add the trusted certificate and SCEP payloads to one configuration profile. This keeps deployment and renewal together.
{% endhint %}

{% stepper %}
{% step %}

### Create the configuration profile

In Jamf Pro, create a **macOS Configuration Profile**. Configure the following payloads before scoping the profile.
{% endstep %}

{% step %}

### Add the trusted root certificate

Download the SCEPman CA certificate from the SCEPman dashboard.

![](https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2Fgit-blob-9170eb0435726398eb43f6fac8abd0d5f35e8cc4%2FSCEPmanHomePage%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(1\)%20\(2\)%20\(1\)%20\(2\).png?alt=media)

Add the **Certificate** payload. Give it a meaningful name, select **Upload**, and upload the CA certificate. Enable **Allow all apps access**.

![](https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2Fgit-blob-d2c01a6e6f5f33ca37ed8f7998b569270fd4dde6%2Fimage%20\(29\).png?alt=media)
{% endstep %}

{% step %}

### Add the device certificate

Add the **SCEP** payload. Enable **Use the External Certificate Authority settings to enable Jamf Pro as SCEP proxy for this configuration profile**.

| Field                      | Purpose                                         | Example                                        |
| -------------------------- | ----------------------------------------------- | ---------------------------------------------- |
| Name                       | Certificate purpose                             | `Device Authentication`                        |
| Redistribute Profile       | Profile renewal interval                        | `14 days`                                      |
| Subject                    | Subject for certificate, additions are possible | CN=$JSSID,OU=computers,CN=$PROFILE\_IDENTIFIER |
| Allow export from keychain | Private-key export                              | No                                             |
| Allow all apps access      | Certificate access                              | Yes                                            |

Adjust the remaining payload options for your certificate use case. Scope the profile to the computers that require the certificate.

<figure><img src="https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2FDPXKt0yJZDkMC0HNqxML%2Fimage.png?alt=media&amp;token=f046e588-36f9-4d70-ba48-d59b9f82c8d5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Verify deployment

Use **Keychain Access** on the target Mac. Check the **System** keychain for both certificates. Jamf Pro also reports the profile status.

![SCEPman Root Certificate](https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2Fgit-blob-b0e61c04f7257e9c5d07a6b51dcc9ae5f3596af3%2Fimage%20\(31\).png?alt=media)

![Device Certificate](https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2Fgit-blob-14a9a4e0f884e9040e639c6a0d48e3e4042f7dee%2Fimage%20\(32\).png?alt=media)
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scepman.com/certificate-management/jamf/computers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
