[
https://issues.apache.org/jira/browse/DIRSTUDIO-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695333#comment-16695333
]
Stefan Seelmann commented on DIRSTUDIO-1199:
--------------------------------------------
Found the cause. The entry returned by the LDAP API is converted to JNDI. The
convert method does not check if the attribute is binary/HR or not:
https://github.com/apache/directory-ldap-api/blob/master/ldap/model/src/main/java/org/apache/directory/api/ldap/model/entry/AttributeUtils.java#L724
> 2.0.0-M14 doesn't display objectGUID / objectSid correctly
> ----------------------------------------------------------
>
> Key: DIRSTUDIO-1199
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1199
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 2.0.0-M14
> Environment: Linux, Debian 9.5, Samba 4.5.12
> Reporter: Samo Forus
> Assignee: Stefan Seelmann
> Priority: Major
> Fix For: 2.0.0-M15
>
> Attachments: m13.png, m14.png
>
>
> In Apache Directory Studio _2.0.0-M14_ *objectGUID* is displayed as "Invalid
> GUID", *objectSid* as "Invalid SID" for a Samba 4 AD. In Apache Directory
> Studio _2.0.0-M13_ both attributes are displayed correctly, as seen on
> screenshots.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
