Return-Path: 
 <dev-return-40826-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
X-Original-To: apmail-directory-dev-archive@www.apache.org
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9B31092CE
	for <apmail-directory-dev-archive@www.apache.org>;
 Sat, 28 Apr 2012 10:20:17 +0000 (UTC)
Received: (qmail 23608 invoked by uid 500); 28 Apr 2012 10:20:17 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 23162 invoked by uid 500); 28 Apr 2012 10:20:12 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 23131 invoked by uid 99); 28 Apr 2012 10:20:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Apr 2012 10:20:11 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Apr 2012 10:20:08 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 7FA05425A84
	for <dev@directory.apache.org>; Sat, 28 Apr 2012 10:19:48 +0000 (UTC)
Date: Sat, 28 Apr 2012 10:19:48 +0000 (UTC)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: 
 <1155833998.6157.1335608388524.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1939028110.8165.1335247064301.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DIRSTUDIO-807) How to support Dot character in
 attribute name
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Emmanuel Lecharny commented on DIRSTUDIO-807:
---------------------------------------------

Hi,

if underscore was allowed in an attributeType name in 1.5.x, it must have been a bug. In any case, it's not anymore the case. I'd like some evidence that we ever accepted underscores in AttributeType names, though...

In the mean time, *none* of the standard AD AttributeTypes, I mean, *none*, contain either an underscore, a dot, or a space  (see http://msdn.microsoft.com/en-us/library/ms675090%28v%3dVS.85%29.aspx). The fact that your users have created some new AttributeTypes with non-compliant names just demonstrates how badly LDAP compliant can be AD.

Now, if you try to find another LDAP server support those forbidden chars in AttributeNames, I wish you a good luck. 

<rant>
In any case, we won't impair our code to support something that Microsoft has deliberately made incompatible with the LDAP specification. Microsoft users have to pay twice for their choice :
- the first time by paying an insane amount of money for their software
- the second time when they run away from Microsoft products just because they are not good enough and have to transform their data to get back in a world of compatibility and open standards.
</rants>

                
> How to support Dot character in attribute name
> ----------------------------------------------
>
>                 Key: DIRSTUDIO-807
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-807
>             Project: Directory Studio
>          Issue Type: Question
>            Reporter: pradip sonar
>
> I am using apacheds-1.5.6 and ApacheDirectoryStudio-win32-1.5.2.
> I am facing issues while trying to add new attribute name containing dot character(.).
> I found that ldap does not support for dot character in attribute name.
> Can you please suggest any configurations needs to be done in apache directory server/studio to support dot character in attribute name?

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