#2132 Improve detection of the right domain when processing group with members from several domains
Closed: Fixed None Opened 7 years ago by jhrozek.

Currently the detection of what domain the group member belongs to in case a group contains members from master domain and subdomain is hackish. We need to improve it as a subtask of #2064


Fields changed

priority: major => critical

Pavel, I have a good idea on implementing the patch and I think this would be a nice self-contained task to start with.

owner: somebody => preichl

Can you also share the idea? :-)

a) finish the patch already on the list to return length of DN that matched and select the longest match
b) use ldap_explode_dn

A unit test for sss_ldap_dn_in_search_base would be also nice while we're touching the code.

Fields changed

description: Currently the detection of what domain the group member belongs to in case a group contains members from master domain and subdomain is hackish. We need to improve it as a subtask of 2064# => Currently the detection of what domain the group member belongs to in case a group contains members from master domain and subdomain is hackish. We need to improve it as a subtask of #2064

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Fields changed

changelog: => N/A, this is internal change to make the code more robust.

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.11.3

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

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