Hi Bruniche,

Thanks for raising the concern. I will check on your query internally and get back.

Hello Bruniche,

Please find below some Support Articles related to your query:-

PowerEdge: How to Generate a CSR using iDRAC9 Redfish: https://www.dell.com/support/kbdoc/en-us/000197810/how-to-generate-a-csr-using-idrac9-redfish

Generate a Certificate Request: https://infohub.delltechnologies.com/en-us/l/methods-to-manage-web-server-certificates-on-idrac/generate-a-certificate-request/

For any additional query, Request you to kindly share detailed info on what exactly you are trying to do and the issue you are facing so we can engage our backend team for a solution if required. If the concern is regarding a particular 17G Server Model, You may raise a Support Case with our Local Support Team on that particular tag through Phone/Online. This will help us collect more info on Phone/Email and assist you further as per your specific requirement.

Hello @Dell-Jai S​

I know how to generate a CSR in redfish with usual parameters.

My issue here is on iDRAC10, the security is higher than on iDRAC9 by default (which can be consider as normal)

What i wish for the redfish call for "GenerateCSR" is that we can also used the following parameters :

KeyPairAlgorithm / KeyBitLength / KeyUsage (as described in your  API iDRAC10 doc i link before) that will allow me to generate a less restrictive CSR than actually.

Like this, by default, nothing change, but if the "end user" want something else because he has another constraint with his own PKI, he still can use your API call.

Thanks.

Hi Bruniche,

To help us understand your requirement better and engage the appropriate backend team, could you please provide more details about the specific changes you are looking to achieve using the KeyPairAlgorithm, KeyBitLength, and KeyUsage parameters in the iDRAC10 Redfish GenerateCSR action?

Additionally, please share an example of the expected CSR configuration or the Redfish request payload you are trying to use, along with any relevant error messages or unexpected behavior you encounter.

This information will help us understand your use case and investigate the feasibility of the requested configuration.

Thank you for your cooperation.

Hello @Dell-ArunK 

I already explain what i want twice & which parameters i would like to have/work in the API call.

There are already present in the DELL API documentation i link before:

But seems ignore during call.

What i want it's that possible to use them to generate a certificate according the user wish (RSA 2048 & not 3072 AND key usage Non Repudiation, Key Encipherment & not Non Repudiation, Key Encipherment, Data Encipherment, which are not the default value on iDRAC 10).

Thanks

Hi Bruniche,

The documented iDRAC10 1.20.xx attribute registry lists the configurable CSR key sizes as 3072 and 4096 bits, with 3072 as the default. That means RSA 2048 is not available through that particular configuration attribute. We have to further check with our L3 and Engineering team on this and get back to you.