SSSD / sssd

#1554 sss_seed should not allow blank passwords
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

This was found by Amith during his testing.

Currently, the SSSD allows the user to enter a blank password. But the SSSD does not allow blank passwords because their semantics is "anonymous bind", which is not allowed in the SSSD.

Sorry, the description should read "should not".

summary: sss_seed should now allow blank passwords => sss_seed should not allow blank passwords

Michal already posted a patch on the list. Moving to 1.9.1.

owner: somebody => mzidek
patch: 0 => 1

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.1

Fields changed

rhbz: => 0

fixed in master 2be3f0fb6f38042386975111a1e86e7b5850ac85

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.9.1

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/2596

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.
Metadata
None
None
None
Normal
defect
SSSD
1.9.0
0
1
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.