SSSD / sssd

#684 limit number of simultaenous krb5 children allowed
Closed: Invalid Opened by simo.

Closed: Invalid
Reopen Issue

Our authentication process create a krb5_child process each time a user authenticates.
Some serialization/limit should be added to the auth provide to avoid issues if too many authentications hit the daemon at the same time.

This might be related to (or resolved by) ticket #533.

component: SSSD => Kerberos Provider
tests: 0 => 1

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.6.0
priority: major => minor

Fields changed

coverity: =>
owner: somebody => jhrozek
upgrade: => 0

Right now there is a queue for each user which allows only one auth request per user at a time. I don't think more limitation is a good idea.

Moving to NEEDS_TRIAGE to make the decision.

milestone: SSSD 1.6.0 => NEEDS_TRIAGE

Fields changed

resolution: => wontfix
status: new => closed

Fields changed

milestone: NEEDS_TRIAGE => void

Metadata Update from @simo:
- Issue assigned to jhrozek
- Issue set to the milestone: void

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to 0

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to 0

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

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
High
defect
Kerberos Provider
1.4.1
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.