IBM Cloud - Structured Ideas
Hide about this portal
This portal is to open public enhancement requests against IBM Cloud and its 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.
IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.
Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Customer response provided by @Oliver Rebmann
Please clarify if the requirement is only to allow a non-reversible deactivate operation where the secret cannot be transitioned back to an active state and can only be later deleted, or the requirement is to provide a disable/enable feature with the secret being able to transition back to an active state? Key Protect referenced as an example for supporting such functionality in the aha! Idea offers key disable/enable api, so I assume the later.
The requirement includes the deactivation and also the activation. In case of issues during hypercare phase after deactivating a secret, it must be possible to activate the secret again to solve the incident.
Add API and UI support for disable/enable of secrets in Secrets Manager.
required
Disabled secrets will include their metadata but not include its credentials when obtained from Secrets Manager.
I do not fully understand this, but it must be possible to enable/activate the secret again as is was before.
Secret types that are managing credentials in integrated services that supports disabling credentials such as IAM Credentials will disable the secret API Keys in IAM.
I do not fully understand this dependency.
Secrets configured with auto-rotation enabled and are disabled at rotation time will not auto rotate. Auto-rotation will resume if the secret will be enabled later and the secret will transition into an active state.
Sounds plausible.
Manual rotation of disabled secrets will not be possible.
Sounds plausible.
Disabled secrets will not send secret life-cycle event notifications (such as secret about to expire, or secret expired). Notifications will resume if the secret will be enabled later.
Sounds plausible.
Additional clarifications and technical information are required for the Secrets Manager team to properly scope and assess the idea. Let me know if the following assumptions are in line with the customer ask:
Please clarify if the requirement is only to allow a non-reversible deactivate operation where the secret cannot be transitioned back to an active state and can only be later deleted, or the requirement is to provide a disable/enable feature with the secret being able to transition back to an active state? Key Protect referenced as an example for supporting such functionality in the aha! Idea offers key disable/enable api, so I assume the later.
Add API and UI support for disable/enable of secrets in Secrets Manager.
Disabled secrets will include their metadata but not include its credentials when obtained from Secrets Manager.
Secret types that are managing credentials in integrated services that supports disabling credentials such as IAM Credentials will disable the secret API Keys in IAM.
Secrets configured with auto-rotation enabled and are disabled at rotation time will not auto rotate. Auto-rotation will resume if the secret will be enabled later and the secret will transition into an active state.
Manual rotation of disabled secrets will not be possible.
Disabled secrets will not send secret life-cycle event notifications (such as secret about to expire, or secret expired). Notifications will resume if the secret will be enabled later.