[
https://issues.apache.org/jira/browse/DIRSTUDIO-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159492#comment-13159492
]
Stefan Seelmann commented on DIRSTUDIO-748:
-------------------------------------------
Numeric OID is defined differently in RFC 4522 and RFC 4512:
RFC 2252 allows OID with leading "0":
d = "0" / "1" / "2" / "3" / "4" /
"5" / "6" / "7" / "8" / "9"
numericstring = 1*d
numericoid = numericstring *( "." numericstring )
But RFC4512 does not:
DIGIT = %x30 / LDIGIT ; "0"-"9"
LDIGIT = %x31-39 ; "1"-"9"
number = DIGIT / ( LDIGIT 1*DIGIT )
numericoid = number 1*( DOT number )
So maybe we should have a strict and relaxed mode, similar to what we have for
the syntax parser?
> Entry attribute name not displayed correctly in Table Entry Editor.
> -------------------------------------------------------------------
>
> Key: DIRSTUDIO-748
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-748
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 1.5.3
> Environment: Windows XP Pro
> Reporter: Nick Applenet
> Labels: table_editor_attribute_name
> Attachments: ADS-AliasEntry_Table_Editor.jpg
>
>
> Entry attribute name is not displayed correctly in Table Entry Editor.
> Specifically for any entry with LDIF:
> dn: cn=bill,ou=Aliases,dc=example,dc=com
> objectClass: virtualaccount
> cn: bill
> mailacceptinggeneralid: ba...@example.com
> mailacceptinggeneralid: b...@sales.example.com
> mailacceptinggeneralid: b...@example.com
> mailacceptinggeneralid: ba...@sales.example.com
> maildrop: b...@example.com
> owner: cn=SalesAdmins,ou=Groups,dc=example,dc=com
> description: Aliases to bill account
> ...in the Table Entry Editor we see "maildrop" attribute displayed as
> "mailacceptinggeneralid"! So, there are 5 mailacceptinggeneralid attribute
> values displayed, and no "maildrop" attribute values!
> The problem is important because we can't tell which of the displayed values
> of "mailacceptinggeneralid" is in fact "maildrop"!
> This does not happen in any other LDAP Browser/editor we have tried.
> Note that LDIF export works correctly.
> Schema for the above entry is custom and follows, for your reference:
> attributetype ( 1.3.6.1.4.1.25260.1.000
> NAME 'mailacceptinggeneralid'
> DESC 'Defines an address that we accept mail for'
> EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
> attributetype ( 1.3.6.1.4.1.25260.1.001
> NAME 'maildrop'
> DESC 'Defines the address mail goes to'
> EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
> attributetype ( 1.3.6.1.4.1.25260.1.002
> NAME 'mailacceptinguser'
> DESC 'Defines if this user accepts mail'
> EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
> attributetype ( 1.3.6.1.4.1.25260.1.003
> NAME 'aliasInactive'
> SINGLE-VALUE
> EQUALITY booleanMatch
> DESC 'A flag, for marking the alias as not in use'
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 )
> objectClass ( 1.3.6.1.4.1.25260.1.1.100
> NAME 'virtualaccount'
> DESC 'Holds mail info for a virtual account'
> STRUCTURAL
> MUST ( owner $ mailacceptinggeneralid $
> maildrop $ cn )
> MAY ( description $ aliasInactive )
> )
> objectClass ( 1.3.6.1.4.1.25260.1.1.101
> NAME 'maillist'
> DESC 'Virtual account for holding mailing list info'
> STRUCTURAL
> MUST ( mailacceptinggeneralid $
> maildrop $ cn )
> MAY ( owner $ description $ aliasInactive )
> )
> objectClass ( 1.3.6.1.4.1.25260.1.1.102
> NAME 'mailAccount'
> DESC 'Email account details'
> AUXILIARY
> MUST ( mailacceptinguser $
> maildrop $ cn )
> MAY ( mailacceptinggeneralid $ aliasInactive )
> )
> objectClass ( 1.3.6.1.4.1.25260.1.1.105
> NAME 'virtualbox'
> DESC 'Mailbox for system use'
> STRUCTURAL
> MUST ( owner $ mail $
> uid $ cn )
> MAY ( description )
> )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
