Fields changed

coverity: =>
description: https://bugzilla.redhat.com/show_bug.cgi?id=658844

{{{
Description of problem:
A certain number of resource limits can be configured by pam_limits. The constraints are currently stored in /etc/security/limits.conf. See 'man limits.conf' for more details.

There is currently no way to centrally manage these constraints. Please add ability to centrally store and manage these parameters, and to deploy them on systems on the user sessions basis.

From pam developer:

I think the best way how to implement this
central management of limits would be to add the functionality to the
pam_sss module which is part of the SSSD project, or to add a completely
new module (pam_sss_limits or so) for this purpose. Again it should be
maintained as part of the SSSD project.

This bug is inspired by customer case 1239203, but not directly dependent on it.
}}}
=> https://bugzilla.redhat.com/show_bug.cgi?id=658844

{{{
Description of problem:
A certain number of resource limits can be configured by pam_limits. The constraints are currently stored in /etc/security/limits.conf. See 'man limits.conf' for more details.

There is currently no way to centrally manage these constraints. Please add ability to centrally store and manage these parameters, and to deploy them on systems on the user sessions basis.

From pam developer:

I think the best way how to implement this
central management of limits would be to add the functionality to the
pam_sss module which is part of the SSSD project, or to add a completely
new module (pam_sss_limits or so) for this purpose. Again it should be
maintained as part of the SSSD project.
}}}

patch: => 0
rhbz: =>
tests: => 0
testsupdated: => 0
upgrade: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=658844 658844]

Fields changed

type: defect => enhancement

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

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

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.