Description of problem: When using AD backend, Keystone can not handle values for the attributes: ‘objectGUID’ and ‘objectSid’ which hold values of format: ['\x01\x07\x00\x02\x00\x00\x09\x05\x15\x00\x00\x006P~US#\xbd>H&\xfd\x1a\x06_\x00\x00'] How reproducible: Need AD setup to reproduce, so I am going with the issue as reported by the customer. Additional info: Let me know what other data from the customer's environment would be useful.
This is a duplicate of a bug that was recently fixed where Keystone was not handling binary LDAP values. Marking as a duplicate. *** This bug has been marked as a duplicate of bug 1138684 ***