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
Post 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 product management 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 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.
Change Identity Insight to honor Liberty authentication and authorization configuration
We are unable to use Identity Insight v9, iFix006 as obtained from IBM without patching SOAPTransformerServlet and RESTTransformerServlet.
This is because iFix006 implements enhanced security which broke our local app that makes SOAP calls to the II webservices app.
We understand that our local app has to be improved to now pass user credentials on the SOAP calls, but that work cannot be accomplished for several months.
In the meantime we implemented a workaround to turn security off at the webcontainer level by setting special-subject type="EVERYONE" on the webservices stanza in applications.xml. This setting worked in that authentication and authorization validation was skipped at the webcontainer level.
However, both SOAPTransformerServlet and RESTTransformerServlet in the webservices app independently perform authentication and authorization validation regardless of the webcontainer setting, and the SOAP call failed with a 401 Unauthorized.
We were forced to patch the IBM Identity Insight SOAPTransformerServlet and RESTTransformerServlet class files to make them always return favorably from calling utils.authenticate and utils.authorize. These patches worked and the workaround is successfully functioning, albeit without security turned on for the webservices app.
We requested an APAR and fix to SOAPTransformerServlet and RESTTransformerServlet to make them honor the webcontainer settings for authentication and authorization validation as the IBM lab indicated should happen.
However, the IBM lab declined to create an APAR and requested that an RFE be opened. Our position remains that this is a defect in that we were informed that II will use the authentication and authorization feature configuration in Liberty, and clearly, in this case it is not working as expected.
We do not want to continue using our locally patched version of webservices, which is not supported by IBM. This affects hundreds of users that use our application to obtain data from the Identity Insight database via webservices and pipelines.
Do not place IBM confidential, company confidential, or personal information into any field.