IBM System Storage Ideas Portal
This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
We have got a workaround from an IBM technician for that problem:
The certificate needs to be provided as pkcs12 certificate file that also includes the private key.
The certificate needs to be imported into a java keystore file (jks) using the java keytool command.
The jks file needs to be imported via the Service WUI to the DS8k.
1.Cert Chain incl. new HMC server cert.
cat hmc.cert.pem intermediate.cert.pem ca.cert.pem > hmc-chain.cert.pem
2.new PKCS#12 cert chain from step 1 plus HMC private key
openssl pkcs12 -export -inkey hmc.key.pem -in hmc-chain.cert.pem -out hmc.p12 -name ds8k
3.Export PKCS#12 to JKS
keytool -importkeystore -deststorepass [passwd of the jks file] -destkeypass [passwd of the key within the jks file] -destkeystore hmc.keystore -srckeystore hmc.p12 -srcstoretype PKCS12 -srcstorepass [passwd of the pkcs12 file] -deststoretype JKS -alias ds8k
HMC Management> Manage Certificates > Advanced > Import Repository
If your CA generates a PKCS12 certificate you can most likely skip steps 1. and 2. and just export the p12 to a jks.
This worked for us, with a 3072 bit long certificate generated from our CA.
German BSI:
key pairs for the signature of certificates must comply with the recommendations in Part 1 of this Technical Guideline (see [TR-02102-1]).
3.6.1Key lengths
It is recommended to use at least the following key lengths:
RSA 2000 bits use up to 2022 (3)
3000 bits from 2023 up to 2029+
(3) These are the recommended periods of use.
As an interim arrangement, the usage of RSA keys of length at least 2000 bits will however remain compliant with this Technical Guideline through 2023.
There are many ideas with the same problem of too weak certificates,
like:
https://ibm-sys-storage.ideas.ibm.com/ideas/DS80-I-237