FNCM Operator should automate change of directory bind user in GCD

We're requested to change all passwords every 8-12 weeks, which includes the directory bind user. While an update to the ldapbind secret updates the Liberty authentication part, the GCD directory config is not updated.
Proposed approach that could be considered
    •    Prior to changing the password for the current LDAP user in the ldapBind secret, substitute the username/password with a temporary user/password
    •    Then the operator can go and update the Directory Service configuration (in the P8 domain in the case of direct LDAP bind) or IM in the case of SCIM
    •    Then the customer can change the password for the current LDAP user (in their LDAP server, e.g., MSAD, TDS/SDS, etc.)
    •    Then the customer can change the temporary user/password back to the current LDAP user (and the updated password)
(Alternatively, user may have the option to have two ldapbind users interchangeably, given sufficient time to change the AD password of the currently inactive user)
Manually changing LDAPBIND user so often creates effort and is error prone. We appreciate your consideration to allow us to change the directory user id and password through FNCM CR file.

Idea priority

High

Post comment

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.

Shape the future of IBM!

Search existing ideas

Post your ideas

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

Specific links you will want to bookmark for future use

FNCM Operator should automate change of directory bind user in GCD

Please enter your email address

RELATED IDEAS

FNCM Operator should automate change of directory bind user in GCD