#2588 Properly handle AD's binary objectGUID
Closed: Fixed None Opened 8 years ago by sbose.

The Active Directory objectGUID LDAP attribute is returned as a binary value which is currently not handled well be SSSD. There is a string representation defined in [MS-DTYP] section which should be used to store the attribute to the cache. Only the surrounding curly braces should be dropped because they cannot be used for LDAP searches.

Fields changed

owner: somebody => sbose
status: new => assigned

Fields changed

patch: 0 => 1

Note: this ticket should be considered for 1.12.5 depending on the patch size.

milestone: NEEDS_TRIAGE => SSSD 1.13 alpha

I'll leave the ticket open for a bit until we decide if the fix in master is enough or if we want it in sssd-1-12 as well.

milestone: SSSD 1.13 alpha => SSSD 1.12.5

Fields changed

resolution: => fixed
status: assigned => closed

Metadata Update from @sbose:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.12.5

6 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/3629

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.