Learn more about these different git repos.
Other Git URLs
gssproxy and mit krb5 uses cwrap tests (at least in fedora).
So it should not be a big problem to implement for sssd.
It would be simpler to use samba4-dc for testing krb5 provider. But sssd can detect it and some part of krb5 provider cannot be tested. (IIRC password policy or password change).
blockedby: => #2821
This ticket is just partially blocked by #2821.
Some preliminary work can be done.
Tests don't need BZ clone
rhbz: => 0
milestone: NEEDS_TRIAGE => SSSD Continuous integration
Metadata Update from @lslebodn:
- Issue marked as depending on: #2821
- Issue set to the milestone: SSSD Continuous integration
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:
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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)
to comment on this ticket.