Skip to content

[MTM-65209] The Common Name (CN) field in the CSR Subject must exactl… #3952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

[MTM-65209] The Common Name (CN) field in the CSR Subject must exactl… #3952

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/device-certificate-authentication/device-enroll-and-re-enroll.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ On creating a new device certificate the Device enroll API is called. This trigg
* The Device enroll API is used by a device to get a fresh new certificate.
* If no CA is available an error occurred with message `Tenant CA certificate is either missing, expired, or has a validity of less than one year`.
* If tenant's keypair is not found then an error occurred with message `Failed to retrieve tenant keypair`.
* If the request does not contain a valid [CertificateSigningRequest](https://en.wikipedia.org/wiki/Certificate_signing_request) an error will be returned.
* The Common Name (CN) field in the CSR Subject must exactly match the device ID supplied during the device registration process. If the request does not contain a valid [CertificateSigningRequest](https://en.wikipedia.org/wiki/Certificate_signing_request) an error will be returned.

{{< c8y-admon-info >}}
As per [EST standards](https://datatracker.ietf.org/doc/html/rfc7030#autoid-58), the certificate in response is in `PKCS7` format by default. Clients can optionally request for a `PKCS10` format by sending `Accept: application/pkcs10` in the request header.
Expand Down