[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seelmann updated DIRSTUDIO-350:
--------------------------------------

    Fix Version/s: 1.2.0
         Assignee: Stefan Seelmann

Yes, this shouldn't be a big issue. We must ensure to always use the 
LdapDN.getUpName() method. I'll try to fix that tomorrow.

> DS is not properly displaying case of group DN
> ----------------------------------------------
>
>                 Key: DIRSTUDIO-350
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-350
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>         Environment: RCP version, Java 6.0, Tivoli Directory Server
>            Reporter: Pavel Trka
>            Assignee: Stefan Seelmann
>             Fix For: 1.2.0
>
>
> Im not big LDAP expert so I hope this is bug and not my misunderstanding of 
> something LDAP specific feature or something similar.
> We have problems with the way DS is working with case of some parts in DN 
> strings. We have some groups in ldap which have DN that look like this:
> cn=somegroup,ou=groups,DC=EXT,DC=COM
> we need DC in uppercase because of some application and Websphere Application 
> Server rights checking and so these groups are stored with DC in uppercase in 
> LDAP.
> Problem with Apache Directory studio is that with such groups it's workjng 
> like it is stored like:
> cn=somegroup,ou=groups,dc=EXT,dc=COM
> So dc here is converted to lowercase.
> DS is displaying it like this, also when I copy DN to clipboard, export ldif 
> etc, Im still getting dc in lowecase. 
> Even also when Im creating new group and I use existing group as template 
> (and this existing group has DC in uppecase) newly created group is stored 
> with dc in lowercase in ldap.
> I dont know if its specific for Tivoli directory server, but my wish is to 
> have DS working with case of DN exactly like it's stored in ldap ;)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to