IBM Sterling Ideas
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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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, 1. Post an idea 2. Upvote ideas that matter most to you 3. 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 notifications 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.
It seems any user in APIUser can execute any Product service. In our solution we might want to permission different users (identified by an access token , I've raised other Ideas for that) to have different access to services (proxied through the application we have written) e.g. All authenticated can read properties (GET) but hardly any should be able to POST/PUT/DELETE etc. So a method/operation level mechanism would be very useful for these services.
|What is your industry?||Banking|
How will this idea be used?
To allow us to fine-grain authorisation so that users can have different levels of access to REST service endpoints.
Do not place IBM confidential, company confidential, or personal information into any field.