SSSD / sssd

#2822 Integration tests: Use krb5kdc in cwrap enviroment for test
Closed: cloned-to-github by pbrezina. Opened by lslebodn.

Closed: cloned-to-github
Reopen Issue

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).

Fields changed

blockedby: => #2821

This ticket is just partially blocked by #2821.
Some preliminary work can be done.

Tests don't need BZ clone

rhbz: => 0

Fields changed

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:
- https://github.com/SSSD/sssd/issues/3863

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)
Metadata
None
None
None
None
Normal
defect
SSSD
1.13.1
#2821
0
0
0
0
0
0
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.