IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
As part of a new rest API web service calls, we have an access token response length more than 2500 characters and this can't be included as part of body or default HTTP header. As API system is of legacy and used by multiple vendor systems these calls can't be changed from client side.
How will this idea be used?
As customer Restful system is a legacy system with latest oauth2.0 authentication type and it is called by multiple vendors technically changing the existing setup will not be an ideal case here, so from ITX we should be able to provide received access token in next successive business calls e.g. HTTP GET '-URL https://testsystem.com/v1/oauth2/?response_type=code&Authorization=Bearer access_token value(>2500 chars) .
|What is your industry?||Retail|
|What is the idea priority?||High|
|Link to original RFE|