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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Re-enable tool centric access management in Rational Change
With Rational Changes alternative to RDS, direct access to LDAP server (provided in Change 184.108.40.206), it is not longer possible to give access to Change Requests using tool specific means.
Access to Change Requests is maintained using Access Control Lists which currently rely on group memberships. Using RDS, groups were created "inside" or at least "very near to" Rational Change. With direct access to company central LDAP server (like Active Directory), the groups have to be created on these central LDAP servers.
Company central directory servers will not allow usage of tool specific LDAP groups, since that would increase the load on these servers radically and this would bring security related issues. Also, the effort to maintain company central groups would increase drastically. Also, in the near future, identity providers will be separated from access providers in many companies in the near future, so that one single service for authentication and authorization will not exist any more.
There must be a method to set up access to Change Requests inside Rational Change itself, e.g. a tool for maintaining locally created groups.
RDS 220.127.116.11 Apache does not support TLS 1.2, TDS 5.2.1 Tivoli with SDS 6.4 does not support Rational Change, so in order to confirm to security requirements, we have to switch to direct LDAP connection from Change.
Access to an identity provider using a protocol less secure than TLS 1.2 is not allowed any more in almost every company that cares for security
Do not place IBM confidential, company confidential, or personal information into any field.