Learn more about these different git repos.
Other Git URLs
SSS_SEED tool allows a user who is non-existent in the domain to be cached. The user records can be verified from the cache. However, authentication for such user always fails. After the failed login attempt, user entries were found to be deleted from the cache.
Steps to reproduce: 1. Ensure that the system is online. 2. Clear the sssd cache and restart sssd service. 3. Add a user to cache who is not part of domain and provide password when prompted. # sss_seed -D LDAP -n non-domainuser -u 10121 -g 10121 -c "Temporary Non-domain user" -h /home/testuser -s /bin/bash
Result seen: User information exists in cache.
Result seen: Authentication fails. Upon verifying the cache, the user records were found to be deleted.
Expected Result: SSS_SEED tool should allow both existing and non-existent domain users to be cached.
If think this is expected behaviour and not a bug.
I agree with Michal, this is not a supported scenarion.
It also sounds like Amith was logging in online, so the attempt couldn't have succeeded.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => todo
milestone: SSSD 1.11 beta => SSSD 1.12 beta
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 priority: major => minor review: => 0 selected: => sensitive: => 0
This has been opened 3 years ago and we haven't really seen any complains about the current behaviour, deferring.
milestone: SSSD 1.14 beta => SSSD Deferred
I would just close, this is not a supported scenario and nobody really complained about this for several years.
review: 0 => 1
resolution: => wontfix status: new => closed
Metadata Update from @apeetham: - Issue set to the milestone: SSSD Patches welcome
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/2589
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.