This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.
As we've identified that in most cases it is sufficient to block password logins, I will be closing the idea, since this already exists in the product. As soon as SAML, LDAP or OIDC authentication is configured users are no longer able to access the password login page at all on the Tenant Unit.
Hello Mate,
yes, option 1 sounds like best solution for this request.
Kind regards
This seems to be 3 different features
1. Login with password should not be possible on the Tenant Unit once SSO is configured. Please verify if this is already addressing immediate concerns.
2. Not being able to invite users when SSO is configured is being considered as an option, as some companies still want to invite external contributors without adding them to their own SSO
3. Deleting or purging users no longer able to log in via SSO is something we're aware of, however we don't currently see how this could be done automatically. We're considering adding a visible "last logged in" field and probably a filter, as SSO logins don't provide a "directory sync" so the product would just never see such a user again.