Skip to content

Conversation

@WillDyson
Copy link
Contributor

If LDAP is configured in CM, repeated failed password checks can lock user accounts.

After LDAP has been configured or the CM admin password is changed, the CM password check will trigger a failed login each time it is used.

This commit adds checks to ensure the check is skipped each time it is run after the first failure.

This is okay as we don't expect the CM password to be changed back to its default value.

Signed-off-by: William Dyson [email protected]

…ot retried once non-default

Signed-off-by: William Dyson <[email protected]>
@WillDyson WillDyson changed the base branch from main to devel October 4, 2022 11:00
@WillDyson
Copy link
Contributor Author

Tested with CM 7.6.1 CDP 7.1.7 by:

  1. Deploying a basic secured cluster with a non-default CM password
  2. Running the playbook again to ensure idempotency, skipping the following tags:
    --skip-tags database,kerberos,tls,cm,verify,os,jdk,users

After changing the Cloudera Manager password, the password is only checked once – other attempts are skipped.

@wmudge wmudge added the bug POINT - Bugfix entry in the CHANGELOG label Nov 7, 2022
@wmudge wmudge merged commit 4be86aa into cloudera-labs:devel Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug POINT - Bugfix entry in the CHANGELOG

Development

Successfully merging this pull request may close these issues.

3 participants