---
title: "Validating the X.509 Certificate"
slug: "validate-certificates"
status: "new"
updated: 2024-12-13T06:54:39Z
published: 2024-12-13T06:54:39Z
canonical: "docs.zpesystems.com/validate-certificates"
---

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

# Validating the X.509 Certificate

This section provides information on how to validate the platform certificate. Before the validation ensure that the following requirements are met:

- The commands on this guide are to be executed on a trusted Linux system that has these commands available:tpm2_makecredential, curl, jq, scp
- It assumes "nodegrid" is the hostname of the device to be attested, for example defined in /etc/hosts. "nodegrid" can be changed to the device's IP instead.
- An active Nodegrid API ticket is stored in the variable $ticket . This command can be used to get a ticket:

```bash
# Create a Nodegrid API ticket, assuming the password is in variable $NG_ADMIN_PASSWORD
ticket=$(\
  curl -s -X POST \
  https://nodegrid/api/v1/Session \
  --insecure \
  -H 'Content-Type: application/json' \
  -H 'accept: application/json' \
  -d '{"username": "admin", "password": "'"$NG_ADMIN_PASSWORD"'"}' | \
  jq -r .session \
)
```

See the following sections for information about certificate validations:

- [Validate the Platform Certificate](/nodegrid/docs/how-to-validate-the-platform-certificate)
- [Validate Endorsement Key Certificate](/nodegrid/docs/how-to-validate-endorsement-key-certificate)
- [Validate Attestation Key name in the Platform Certificate](/nodegrid/docs/how-to-validate-attestation-key-name-in-platform-certificate)
- [Validate that TPM can use the private part of the Attestation Key to sign](/nodegrid/docs/how-to-validate-that-tpm-can-use-the-private-part-of-attestation-key-to-sign)