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.
OAC login and authorization by means of TAI that populates WSSubject with user and groups
My customer is using a Trust Association Interceptor (TAI) which provides the end user authentication and authorization. The TAI is setting up the Principal (username) and his Groups in the WSSubject. Their federated repository that is configured with WebSphere is only used for admin users and doesn´t contain the users that login to the OAC. The OAC users are authenticated and authorized by the TAI.
However currently the OAC expects its users to be existing in the user repository because the OAC is doing a getGroupsForUser call on the WAS UserRegistry api. This api call will not return any groups for my customer´s configuration and therefore the OAC user login fails. This request is about having the OAC login take the Principal and Groups from the WSSubject (J2EE api) instead of the WAS UserRegistry api.
I have attached sample code (see SampleCode.pdf) that shows how the groups of a user can be retrieved from the WSSubject.
Do not place IBM confidential, company confidential, or personal information into any field.