directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-434) add value editor for Active Directory objectGUID attributes
Date Tue, 06 Oct 2009 10:00:31 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762574#action_12762574
] 

Stefan Seelmann commented on DIRSTUDIO-434:
-------------------------------------------

- Added syntax 2.5.5.10 to binary syntaxes
- Added attribute types objectGUID (1.2.840.113556.1.4.2) and objectSid (1.2.840.113556.1.4.146)
to binary attributes
- Also improved process of reading the schema because there was another issue: We read the
schema from the server and parse object classes, attribute types, matching rules and syntaxes
to schema objects. Active Directory schema only provides object clases and attribute types,
but no syntaxes and no matching rules. The problem is that although both objectGUID and objectSid
contain a syntax OID it is considered as invalid because the target syntax object does not
exist. I fixed that by creating pseudo syntax and matching rule objects in such a case.




> 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.


Mime
View raw message