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:
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 ideasibm@us.ibm.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
This RFE remains on our development backlog but I can't tell you when or if the feature might be released.
Are there any news on this PMR?
I have realised the trusted in a self written Java Class, but I want to get rid of it as soon as possible, because the performance is not really good.
We have a business case, where we would be glad to use identity propagation within cics liberty, so I would be great, if this rfe could be realized!
Although this RFE is specifically for IBM z/OS platform, If this feature request is implemented, it will be for all WAS platforms, z/OS, distributed (Linux, Unix, Windows) and IBM i, similar to the existing support for DB2 trusted context in traditional WebSphere Application Server.
We just implemented the identity propagation by the hand in an custom DB Access Class, but this is really not good. For our needs a very simple identity propagation would be enough and could be done easily by extending the existing datasource:
It should be like a switch to one special clientuser after connecting.
We don't need an identity propagation of every user which made a login.
Regards Peter
My customer uses WebSphere Traditional today with "trusted context" to propagate client identity to DB2 for authorization and audit. We would like to migrate to Liberty in 2017 to benefit from improved performance, flexible administration and production alignment with developer's desire to use Liberty. Liberty will run on z/OS and we prefer the type 4 driver to achieve greater zIIP offload.
Thank you
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Application Platform
Product - WebSphere Application Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Application Servers
Product - WebSphere Application Server