Not sure if I can do it by Christmas (well, 2013 Christmas anyway) but documenting the relationship between the PAC responder, GSSAPI authentication and maybe SSHD would be nice.

As a furhter clarification, Jan didn't mean to document the PAC responder per se, but also what is the relation between SSSD, GSSAPI and Kerberos in several scenarios.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.4
rhbz: => 0
type: enhancement => task

This task should not block the 1.11.4 release. Also I'm bumping the priority to make sure this task is not postponed indefinitely again.

priority: trivial => minor

Fields changed

milestone: SSSD 1.11.4 => SSSD 1.11.5

This task should not block the 1.11.5 release. Also I'm bumping the priority to make sure this task is not postponed indefinitely again.

priority: minor => major

This is a minor task that shouldn't block 1.11.5 and perhaps should be moved out of 1.11.x completely.

milestone: SSSD 1.11.5 => SSSD 1.11.6

Hopefully moving for the last time..

milestone: SSSD 1.11.6 => SSSD 1.11.7

We keep moving this ticket from one minor release to another. Bumping to triage to assign to somebody for real.

milestone: SSSD 1.11.7 => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.2
priority: major => trivial

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

Fields changed

mark: => 0
milestone: SSSD 1.12.3 => SSSD 1.12.4

Moving tickets that didn't make the 1.12.4 release to 1.12.5

milestone: SSSD 1.12.4 => SSSD 1.12.5

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

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.