This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Please backport this API to V7R3.
See https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=145325
APIs are available in IBM i 7.4 to help automate a Let's Encrypt scenario.
The primary API that was provided in IBM i 7.4 to enable the scenario is QycdRenewCertificate. When using this API with format RNWC0300, the updated certificate gets imported into the the DCM certificate store. The automated renewal process with Let's Encrypt uses the original certificate signing request (CSR) to request subsequent certificate requests which means the original private key remains in the DCM certificate store and the new certificate from Let's Encrypt containing the associated public key will replace the old certificate during import. Continually using the existing CSR to receive a new certificate from Let's Encrypt and calling QycdRenewCertificate with format RNWC0300 to import the new certificate is therefore the preferred method to automate the Let's Encrypt scenario.
If the automated process generates a new public/private key pair and new CSR using QycdRenewCertificate format RNWC0100, the import of the certificate
with format RNWC0200 generates a new certificate label. This process requires special handling of the CSR data and requires additional calls to update the certificate assignment for the Application Definitions using QycdRemoveCertUsage and QycdUpdateCertUsage APIs.
DCM is expanding the list of APIs in the future to allow more management of certificates to be done via customized automated applications.
The APIs that can be expected in the future include the following:
1. Update an application with a specified certificate.
2. Check for a certificate associated with an application.
3. Remove a certificate from an application.
4. Add a CA trust relationship with an application.
5. Check for CA trust relationship with an application.
6. Remove CA trust from application.
7. A. Request a certificate to be renewed and get a certificate signing request.
B. Import an issued certificate that was requested for renewal.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Security
Operating system - IBM i
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Web Serving
Operating system - IBM i
Source - None