This is an IBM Automation portal for Integration 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).
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.
See this idea on ideas.ibm.com
The request is to add two additional properties to all credential types. Both properties should display as normal text in the UI tiles or when retrieved by the Rest API. The first property is LastUpdatedDate which would be automatically set when the credential is created or updated. Having this information would make it easier to tell when a credential was created or if it was recently updated. This would be useful in trouble-shooting and auditing. The second property is ExpiresOnDate. This would be a new optional property that could be set when the credential is created or updated. It would be intended to allow the user to record when the credential is set to expire. This would be useful when using expiring credential secrets (i.e. password, client_secret) that must be periodically renewed/refreshed. For example, we could use the Rest API to generate a report showing all credentials that will be expiring in the next 60 days so that we could plan for their renewal. The mqsicredentials command could either strictly enforce the use of standard date formats (i.e. 2024-10-15) or just allow freeform text (i.e. "Expires at midnight on Oct 15, 2004") Either way is acceptable.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for raising this idea Steve and for the brief further discussion that we managed on this topic face to face when we last met. We are moving the status of this suggestion to Future Consideration.
The timestamps mentioned (which clearly each have a distinct purpose) would need to be displayed in the Web UI in order to bring value to the user (so should be treated more like the username part of a credential as opposed to the password part which is deliberately obscured from the webUI admin interface). In terms of implementation we think the extra metadata could be stored in the credential json itself, so this does seem achievable within the constraints of the existing architecture. Thanks for raising - we will watch with interest to see if the idea gains traction from the community.