Learn more about these different git repos.
Other Git URLs
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)
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=742510
owner: somebody => jhrozek
Marking as a duplicate of Ticket #1016
That is a superset of this.
resolution: => duplicate status: new => closed
rhbz: => 0
Metadata Update from @jokajak: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.8 beta
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.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.