[
https://issues.apache.org/jira/browse/DIRSTUDIO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654016#action_12654016
]
Emmanuel Lecharny commented on DIRSTUDIO-434:
---------------------------------------------
The problem is that Microsoft (as usual ...) is using its own syntax. Instead
of using the 1.3.6.1.4.1.1466.115.121.1.40 syntax, they defined a specific one
(2.5.5.10) under an OID which should not be extended... Anyway, we won't change
the way M$ is sabotaging the standards ...
Let's implement M$ syntaxes. The first step would be to list all of them, in
order to avoid doing it again.
> add value editor for Active Directory objectGUID attributes
> -----------------------------------------------------------
>
> Key: DIRSTUDIO-434
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-434
> Project: Directory Studio
> Issue Type: New Feature
> Components: studio-ldapbrowser
> Affects Versions: 1.2.0
> Reporter: Marius Scurtescu
>
> When viewing an Active Directory entry objectGUID attributes are not
> displayed, and it is also not possible to edit them. Same for objectSid, both
> have the same syntax OID. The entry editor just shows "Invalid Data" for them.
> The attributes have binary values. They could be displayed either in hex
> format (and the hex format can be used in searches as well, with a backslash
> in front of every two hex digits), or using the preferred Microsoft format,
> which is just the hex format shuffled and delimited with dashes.
> Here are a couple of articles that show how to convert from hex to the
> Microsoft format:
> http://forums.sun.com/thread.jspa?threadID=646111
> http://blog.joeware.net/2008/05/03/1230/
> (I found this in version 1.3, but this is not listed as a released version)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
