This is an IBM Automation portal for Cloud Platform 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.
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