#2062 Leverage RFC 4533 in server mode for enumeration and synchronization of external groups
Closed: wontfix 2 years ago by pbrezina. Opened 8 years ago by jhrozek.

When the 389DS server gains the ability of persistent searches according to RFC4533, we can use the capability to provide more efficient way of detecting changes in external groups rather than polling for lastUSN changes.

This would be mostly usable in the server_mode.

Here is the 389-DS ticket:

In the meantime maybe we could use the persistent search.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => 0
type: defect => task

Fields changed

mark: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This would make resolving the external groups significantly easier.

priority: major => critical
sensitive: => 0

This ticket is related to #2602. In the server mode, this can be important for the legacy clients who use HBAC data from the server and for resolving external groups. I think it's a minor item for the Alpha milestone.

milestone: SSSD 1.14 beta => SSSD 1.14 alpha
priority: critical => minor

In the Alpha release I would like to focus on splitting the sysdb. This is an incremental improvement which can live in the Beta milestone.

Sorry about the noise.

milestone: SSSD 1.14 alpha => SSSD 1.14 beta

This was a minor enhancement on top of the sysdb writes changes, but unfortunately it didn't make the first cut.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

4 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

2 years ago

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.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 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/3104

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.