This is an IBM Automation portal for Cloud Platform products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
We are assuming the request is for an API to update the LDAP bind passwords. This is already possible using simple wsadmin scripts. If using a Standalone LDAP server you would do the following:
AdminTask.configureAdminLDAPUserRegistry(["-bindDN", bindID, "-bindPassword", bindPwd, "-verifyRegistry", "false"])
AdminConfig.save()
secMBeans = AdminControl.queryNames("type=SecurityAdmin,*").splitlines()
for mbean in secMBeans:
AdminControl.invoke(mbean, "resetLdapBindInfo", [bindID, bindPwd])
If using a federated repository the following can be used instead:
rep = AdminTask.getIdMgrRepository(["-id", "myLDAP"])
AdminTask.updateIdMgrLDAPBindInfo(["-id", rep, "-bindPassword", bindPwd, "-bindDN", bindID])
Hi, I am not sure how the security team is going to reply, but tWAS/Liberty are agnostic how LDAP Servers, DB Servers, JMS Servers, etc store and maintain their passwords. They should comply with industry standards for retrieving data, writing data, but usually each vendor implements a different way of that security is maintained. It would be difficult for tWAS/Liberty to maintain this type of interaction for each vendor. If you have a specific vendor, then your application team should be able to update the password when needed through APIs provided by the vendor. -Brian
Hi, I am not sure how the security team is going to reply, but tWAS/Liberty are agnostic how LDAP Servers, DB Servers, JMS Servers, etc store and maintain their passwords. They should comply with industry standards for retrieving data, writing data, but usually each vendor implements a different way of that security is maintained. It would be difficult for tWAS/Liberty to maintain this type of interaction for each vendor. If you have a specific vendor, then your application team should be able to update the password when needed through APIs provided by the vendor. -Brian