Post by adamp on Jan 24, 2023 10:02:08 GMT
Please consider adding PKCS#1 private key format as a valid option to Certificate related resources.
Currently:
Redfish Data Model Specification 6.16.5.2.2 PEM: "The private key shall be encoded as described in section 10 of RFC7468"
The section 10 of RFC7468 describes only PKCS#8 private key format as a valid option.
Request to add:
PKCS#1 private key format using delimiters -----BEGIN RSA PRIVATE KEY-----, -----END RSA PRIVATE KEY-----
Explanation:
We are going to use original Redfish resources whenever possible in Fujitsu Limited. We are using iRMC server view to manage our Primergy servers.
The iRMC web server accepts PKCS#1 private key along with TLS certificate, therefore PKCS#1 support in Redfish is needed to use Certificate related resources.
Currently:
Redfish Data Model Specification 6.16.5.2.2 PEM: "The private key shall be encoded as described in section 10 of RFC7468"
The section 10 of RFC7468 describes only PKCS#8 private key format as a valid option.
Request to add:
PKCS#1 private key format using delimiters -----BEGIN RSA PRIVATE KEY-----, -----END RSA PRIVATE KEY-----
Explanation:
We are going to use original Redfish resources whenever possible in Fujitsu Limited. We are using iRMC server view to manage our Primergy servers.
The iRMC web server accepts PKCS#1 private key along with TLS certificate, therefore PKCS#1 support in Redfish is needed to use Certificate related resources.
