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.
Allow for generic or service accounts that don't expire passwords for systems making calls
Either allow for generic or service accounts with non-expiring passwords or allow for other authentication means for apps that are making calls. Resetting every x days is intrusive.
|
What is your industry?
|
Banking
|
|
How will this idea be used?
A user could integrate an app like Salesforce that makes REST API calls to PEM and issue a service account that doesn't have an expiring password, so they don't need to reset/change it quarterly.
A user could integrate an app like Salesforce that supports token-based auth or key-based auth and use that rather than a password.
|
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.
Guest
PEM calling PEM APIs can now use the internally-generated token authentication, and this is working.
External system calling PEM as described in the original request, still requires changing the password every 90 days. There is no way to create a service account with a non-expiring password.
One solution is a randomly generated API key that is only displayed once and functions as a password. Another solution is implementing SSO or LDAP authentication so the internal PEM user database is not used. Both these approaches are used in many large SaaS offerings.
We intend to address this requirement in an upcoming release.
We intend to address this requirement by supporting the use of tokens for the API Configurations. This will allow the primary sponsor administrator to choose to support tokens rather than user name and password. This will remove the need for the primary sponsor administrator to have to update the passwords on the various API Configurations when they update their login password.