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.
I totally agree. Command approval is a very good and necessary feature, but after the first, seemingly hurried implementation, it needs to be made robust.
Not only should it be prevented that administrators promote themselves a approvers, but also promoting other administrators should be restricted. Otherwise, an administrator "Admin1" with system privilege who is *not* a command approver can simply do:
register admin Admin2 pw cmdapprover=yes
This administrator can then issue restricted commands as "Admin1" and approve them his/herself as "Admin2".
To prevent this, "set commandapproval on" should also make the commands "register admin" and "update admin" restricted.
(In addition, the command "set commandapproval on" should work only if there is at least one approver administrator already defined, otherwise administrators could lock themselves out.)
There is a related "idea" https://ibm-sys-storage.ideas.ibm.com/ideas/SPF-I-2366 mentioning that "register admin", "update admin" and "remove admin" should also be restricted commands.
I'd say that this is a defect as it indeed defeats the purpose of the Approver functionality.
This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.