#946 RFE: Allow netgroups to have a different expiration time than users
Closed: Duplicate None Opened 12 years ago by jokajak.

We have a local need to update netgroup entries more rapidly than user entries so we would like to be able to specify the expiration timeout for netgroups independently of users.


Should we in general introduce different timeouts per map type? As we add support for more map types that might become a useful feature.

Yes, I think we should add {{{$MAP_entry_cache_timeout}}} for each map type we support, falling back to using {{{entry_cache_timeout}}} for any map not explicitly set. (Similar to how we do search bases in the LDAP provider for users, groups and netgroups).

component: SSSD => NSS
priority: minor => major

This is related to other work we are going to do with different maps in 1.8.

milestone: NEEDS_TRIAGE => SSSD 1.8.0

This is related to other ticket: #1016

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.8.0 => SSSD 1.7.91 (1.8.0 beta 1)

Fields changed

owner: somebody => jhrozek

Marking as a duplicate of Ticket #1016

That is a superset of this.

resolution: => duplicate
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @jokajak:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.8 beta

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

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.

Metadata