#1807 [RFE] authenticate against cache in SSSD
Closed: Fixed None Opened 7 years ago by dpal.

https://bugzilla.redhat.com/show_bug.cgi?id=910187 (Red Hat Enterprise Linux 6)

allow cache authentication in sssd instead of authenticating directly against
network server every time.  authenticating against the network many times can
cause excessive application latency.

There might be another ticket related to this case.

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.11 beta
selected: =>
testsupdated: => 0

This was requested again in ticket #2408, so apparently this is something our users would like to see.

To quote from that ticket:


sssd-ldap caches your credentials while the LDAP server is offline. But I'd like to have them cached while it's online too. There are some cases where you need to authenticate often (like Subversion over Apache). This would help speed things up, and reduce the load on the LDAP server.

The time should be configurable.


changelog: =>
review: => 0

Fields changed

cc: => jacob@jacobweber.com

This was requested again, so I'm bumping the ticket to NEEDS_TRIAGE. It's unlikely we ca squeeze it to 1.12, but we might want to prioritise it in 1.13 better.

milestone: SSSD 1.13 beta => NEEDS_TRIAGE

As discussed on the SSSD meeting last Thursday, we are moving the ticket back to 1.13 for capacity reasons. However, I'm bumping the priority as this functionality is requested periodically.

mark: => 0
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
priority: major => critical

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 alpha

Fields changed

cc: jacob@jacobweber.com => jacob@jacobweber.com, niklas.andersson@openforce.se

Fields changed

owner: somebody => preichl

Fields changed

patch: 0 => 1

The patch is under review, but we won't block the alpha release over it.

milestone: SSSD 1.13 alpha => SSSD 1.13 beta
sensitive: => 0

Fields changed

milestone: SSSD 1.13.1 => SSSD 1.13.0

resolution: => fixed
status: new => closed

Metadata Update from @dpal:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.0

3 years ago

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

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.

Login to comment on this ticket.