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.
@Brian, Checking on this. It was conveyed to me in December that it would be put into the roadmap for 2023 by the AoC PM. Can you give me any update on this? It is our #1 T1 support ticket issue (Then Aspera Connect installs is a very distant #2).
Basically, when you send a package to someone, they get a user auto-created. So what's the real difference with sending a package to a deactivated user? I get 1 use case where a deactivated user is being actively blocked through that deactivation. Not here. We need our workspace owners to make this decision, but also the Org Admin to allow it as well. PLEASE get this through asap since I see no indication on "Coming Soon" that it is indeed coming (actually that page is now blank in AoC).
Got it. Moving it over for future consideration. Thanks
Brian,
it may be a bug but the users should become deactive as they are past the "Consecutive days without login" deactivation period. It's just that I would expect in the case of a SAML user they could just log back in and become active again without an admin manually making them active.
Hi - This sounds like a bug where a user should not be auto deactivated if originally active. Can you please open a support ticket and we can have engineering investigate it?