This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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).
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:
Search existing ideas
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 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
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
We understand that ServiceNow OAuth authentication is a three-way process, Workbench, after initial Oauth handshaking, submits a third party credential to be responsible for the actual queries. We also understand that currently, the third party credential supplied is the user currently logged in to Workbench (just as it is to git for commits, and to DataStage for DS operations) After authentication, queries use the Service Now API via https GET requests.
At Huntington, ServiceNow operates under a policy that only limited accounts have access to the API interface, it is not granted to general user populations, but rather only to role accounts, with very limited exceptions, which are sunsetted (so no new exceptions will be granted)
So Workbench needs to supply one of these role account credentials, but does not currently have a way to retain these in the ServiceNow configuration. The current temporary configuration where specific users are granted access to the API is not allowed by policy, it was only enabled temporarily to aid with debugging
The enhancement request is to add the ability for the ServiceNow configuration to retain a user id and secret to be used for this purpose, and that the UI be enhanced to let admin users manipulate these, with appropriate masking, as is done elsewhere in Workbench configuration. Allowing the secret part of these credentials to be kept in the .secrets directory (via the ${file ...} construct) adds convenience and avoids having plaintext credentials in the issue management yaml file, but that's optional
Needed By | Yesterday (Let's go already!) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.