Fields changed

description: The solution should include:
* Utility to take a password and produce an obfuscated password as a string that can be put into the configuration file
* Add a logic to support a new configuration value (obfuscated password) in the configuration file for LDAP back end
* Change to the back end to ignore plain text password configuration value if it is present when the obfuscated password value is present.
* Decrypt the obfuscate password before establishing an LDAP connection
* Implement netgroups support since Visa uses netgroups for the access control
=> The solution should include:
* Utility to take a password and produce an obfuscated password as a string that can be put into the configuration file
* Add a logic to support a new configuration value (obfuscated password) in the configuration file for LDAP back end
* Change to the back end to ignore plain text password configuration value if it is present when the obfuscated password value is present.
* Decrypt the obfuscate password before establishing an LDAP connection

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.4.0

Fields changed

owner: somebody => jhrozek

I assume that the obfuscate password is a string which contains only printable ASCII characters. If this is true this option can also be used to encode binary passwords or password with unprintable characters. A simple base64 encoding would be enough for this use case, but instead of implementing both this would be "another" useful purpose for the obfuscate password option.

Fields changed

status: new => assigned

Fixed by
- 69aaef8719c5cf33ed1c4090fa313ba281bf8a02
- 2e6087c6cc903d5164b9a1d5e3d791fd046001d9
- 4f5405595730a106f7406eba849f65cda2eb53f1
- 530ba03ecabb472f17d5d1ab546aec9390492de1
- 88aeed9a31b734a92630d5e881c960c5f77ba0ce

fixedin: => 1.4.0
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1605

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.