> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-smime-certificates/phase-1-steps/step-2-certificate-signing-request.md).

# Step 2 - Certificate Signing Request

A CSR contains the public key and identity information needed to create your certificate. On this screen you either provide your own CSR (if your IT team generated one) or allow the system to generate the key pair for you.

<figure><img src="/files/siwvLev4MTTIs1N62blI" alt=""><figcaption></figcaption></figure>

&#x20;

#### Important Note About the CSR

**NOTE**:  The public key and signature algorithm from your CSR are used for certificate generation. Subject details such as Organisation, Country, and State are pre-filled from your CSR for convenience, but you can edit them. The values you submit in this form will be the final values in the issued certificate.

#### Field Reference

•        Key Generation (\*): Specifies who generates the cryptographic key pair (public and private keys). Select 'Requester' if your IT team or you will generate the CSR. If you are unsure, keep the default.

•        Skip CSR: A checkbox that, when ticked, bypasses the CSR upload and lets the system generate the key pair for you. Tick this checkbox ONLY if instructed by your administrator and you do not have a CSR ready.

•        Upload CSR: Allows you to upload a CSR file directly from your computer. Click 'Choose File', navigate to your CSR file (usually a .csr or .pem file), and select it.

•        Paste CSR: A text area where you can paste the contents of your CSR directly. Open your CSR file in any text editor (e.g. Notepad), select all the text (Ctrl+A), copy it (Ctrl+C), and paste it here.

&#x20;

**WARNING**:  Never share your private key with anyone, including CERTInext support. Only the CSR (which contains the public key) is submitted here. Your private key must remain on your computer.

**NOTE:**  If you are using a CSR generated by your IT department, they will provide you with the CSR file or text to paste here.

#### What to Do

•        Set Key Generation to 'Requester' (default).

•        Choose one of the two options:

◦        Option A (Upload): Click 'Choose File' and select your .csr or .pem file.

◦        Option B (Paste): Open your CSR file in a text editor, copy the full text, and paste it into the 'Paste CSR' box.

•        If you do not have a CSR, tick 'Skip CSR' and the portal will generate one for you.

•        Click Next.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-smime-certificates/phase-1-steps/step-2-certificate-signing-request.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
