> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/adding-new-or-renewing-existing-certificates-to-controllers-using-802-1x.md).

# Adding new or renewing existing certificates to Controllers using 802.1x

### Introduction

Once a Controller has been configured for 802.1x, new certificates can be added or existing certificates can be renewed in Command Centre Configuration Client using the following procedure.

**Note:** When renewing a Client certificate, a Certificate Signing Request (CSR) needs to be generated first for the roll-back feature to be supported.

***

### Configuration

1. In Command Centre, click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Controller you want to add a new certificate to, or renew an existing certificate for.
3. **Right click** and select **Properties**.
4. Click the **Network** tab.

   The **General** sub-tab displays by default.
5. Click the **802.1x** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1b600ed96fae68491f8955a1d7d0098baed86a8a%2Fcontroller7000_networktab_802.1x.png?alt=media)
6. Click the **Generate CSR** button.

   A new certificate request is generated in a 'read-only' text format which can be either copied manually to a file, or can be exported using the **Export CSR** option which becomes available once after the CSR is generated.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-889968e9bbd3dba807c0486717d6fa96555ad7fd%2Fcontroller7000_networktab_802.1x_exportcsr.png?alt=media)

   When a new CSR is generated, a waiting message appears at the bottom of the page as a guide through to the configuration process.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-205f16e445cca70bbaa0d8a2881928b1e8268673%2Fcontroller7000_csrgeneratedmessage.png?alt=media)

   When a file has been selected, the **View Certificate** buttons appear to the right of the **Upload File…** buttons, and the **Update Configuration** button is enabled.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7e5707f82c519bad0b00962582658196424cae79%2Fcontroller7000_networktab_802.1x_viewcertificate.png?alt=media)

   The **View Certificate** buttons enables you to view the recently uploaded certificate, (i.e. Server Certificate or Client Certificate as appropriate).
7. Click the **Update Configuration** button to start the process of downloading the certificates to the Controller.

   **Note:** Alarms are generated if the signed certificate is expired, doesn’t match the Private Key, or doesn’t contain a valid Subject

   Alternative Name (SAN) or Extended Usage extension as the CSR. These alarms can be processed.
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/adding-new-or-renewing-existing-certificates-to-controllers-using-802-1x.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.
