For the complete documentation index, see llms.txt. This page is also available as Markdown.

Generate CSR (WLAN Only) - Command 0xEF03

The host uses this command to generate a certificate signing request (CSR) in PEM format. The CSR generated will be saved to volatile memory in the device and will overwrite any existing CSR. The CSR will persist in volatile memory until it is overwritten, fetched with Start Get File from Device - Command 0xD821 or the device is power cycled or reset.

The sequence of events is as follows:

1

Generate CSR — Step

The host will use Generate CSR keys (WLAN Only) - Command 0xEF02 if it wants generate a CSR using a new CSR key pair.

2

Construct and send request

The host constructs the command request in the format below and sends it to the device.

3

Device response

The device sends a response in the format below to the host to indicate that CSR generation has completed.

4

Fetch CSR

The host fetches the CSR with Start Get File from Device - Command 0xD821.

5

Create certificate

The CSR is used to create a certificate.

6

Load certificate into device

The host loads the certificate into the device with Start Send File to Device (Secured) - Command 0xD811.

Request Data for Command 0xEF03 – Generate CSR (WLAN Only)

Tag
Len
Value / Description
Typ
Req
Default

Beginning of any wrappers, at minimum including Request Message

EF03 = Generate CSR (WLAN Only) - Command 0xEF03

81

1

Key Identifier The key identifier to use to generate the CSR. The key pair associated with the identifier must already be present in the device for the command to succeed.

0 = CSR keys

1 = Apollo server cert keys

2 = Customer server cert keys

3 = Commercial server cert keys 4 = Apollo client cert keys

B

O

0

82

var

Subject

Including this optional parameter will override the default subject. This parameter should contain a null terminated string. This string should contain a list of attributes separated bycommas. If an attribute’s value contains a comma, the comma should be replaced with “\,” Each attribute value should be prefixed with its attribute name followed by “=”. The following is a list of valid attribute names.

"CN" "commonName" "C" "countryName” "O" "organizationName" “L” “locality” "R" “OU” "organizationalUnitName" “ST” "stateOrProvinceName" "emailAddress" "serialNumber" “postalAddress” "postalCode" “dnQualifier” "title" “surname” "SN" “givenName” "GN" “initials” "pseudonym" "generationQualifier" “domainComponent” "DC" “O=MagTek Inc,CN= test1.com” is an example with two attributes.

“serialNum ber=XXXX XXX,CN= df- xxxxxxx” where XXXXXX X is Property 2.2.1.1.1.1****Serial Number and so is xxxxxxx but in lower case

83

var

Subject Alternative Names

Including this optional parameter will override the default subject alternative names. This parameter should contain a null terminated string. Only DNS names and IP addresses are supported and only a maximum of two each. DNS names must be prefixed with “DNS=” and IP addresses must be prefixed with “IPA=”. All Subject Alternative Names

Must be separated with a comma and not spaces. Subject Alternative Names may not be ordered in the CSR the same as they are ordered here.

"DNS=test1.com,DNS=test2.,IPA=1.10.16.255,IPA=2.10.16.25

4" is an example.

B

O

“DNS=df-

xxxxxxx,IP A=192.168

.0.1where xxxxxxx is Property 2.2.1.1.1.1

Serial Number but in lower case

End of any wrappers, at minimum including Request Message

Response Data for Command 0xEF03 – Generate CSR (WLAN Only)

Tag
Len
Value / Description
Typ
Req
Default

Beginning of any wrappers, at minimum including Response Message

EF03 = Generate CSR (WLAN Only) - Command 0xEF03

No parameters.

End of any wrappers, at minimum including Response Message

Request Example - Command 0xEF03

Response Example - Command 0xEF03

Last updated