Learn more about these different git repos.
Other Git URLs
When a response from LDAP server is received, an automatic conversion is done according to map that has been used. That way, attributes stored on LDAP server are unified and transformed into attributes we use in sysdb. Sysdb names are then used during the following processing of these attributes.
The problem is that at some places we use map[SDAP_AT_].sys_name to refer to attribute name and at some other places we use SYSDB_ constants. The latter one can cause problems in case the SYSDB_* constant is changed in the map and not in the code that is expecting the original attribute name. Therefore only the first form should be used except for those cases when we are creating a sysdb attribute that doesn't have its LDAP counterpart.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.9.0 NEEDS_TRIAGE type: defect => task
"Nice to have" for 1.9.
milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD 1.9.0
rhbz: => 0
feature_milestone: => owner: somebody => mzidek proposed_priority: => Undefined
There is no real value to do this change. Thus closing.
resolution: => wontfix status: new => closed
Metadata Update from @jzeleny: - Issue assigned to mzidek - Issue set to the milestone: SSSD 1.9.0
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/2162
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.