hilscher NIOT-E-TPI51-EN-RE, User Manual

Page: 222 / 258

Public Key Infrastructure 222/258
16.2.3 File formats for certificate and key files
The Edge Gateway uses the PEM file format (Privacy Enhanced Mail
according to RFC1421 to 1424) to store certificate and key files.
PEM file format
Certificate and key files for use in the PKI of the Edge Gateway use the
Base64-coded PEM file format. Within this format, the genuine Base64-
coded certificate data are surrounded by
-----BEGIN CERTIFICATE-----
at the beginning and
-----END CERTIFICATE-----
at the end of the PEM file.
Similarly, key data are surrounded by
-----BEGIN RSA PRIVATE KEY-----
and
-----END RSA PRIVATE KEY-----
.
you can convert a Base64-coded
*.CER
or
*.CRT
file into the
*.PEM
format, by following these steps:
Ø
Surround the Base64-coded genuine certificate data with
-----BEGIN CERTIFICATE-----
at the beginning and
-----END CERTIFICATE-----
at the end.
Ø
Surround the Base64-coded genuine key data with
-----BEGIN RSA PRIVATE KEY-----
at the beginning and
-----END RSA PRIVATE KEY-----
at the end.
Ø DChange the file extension
*.CER
or
*.CRT
to
*.PEM
.
16.3 Use cases
There are three use cases for working with root, client and server certicates
and the associated private keys within the public key infrastructure:
Use case 1: Verification of the authenticity of the communication partner
(Server)
[ } page 223]
Use case 2: Server certificates for Edge Gateway services [ } page 224]
Use case 3: Client certificates for specific servers [
}
page 226]
Edge Gateway | NIOT-E-TPI51-EN-RE (Connect)
DOC170502UM04EN | Revision 4 | English | 2018-08 | Released | Public © Hilscher 2017 – 2018