Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 195CB200C67 for ; Mon, 15 May 2017 15:48:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 16563160BC1; Mon, 15 May 2017 13:48:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5E164160BD1 for ; Mon, 15 May 2017 15:48:09 +0200 (CEST) Received: (qmail 51195 invoked by uid 500); 15 May 2017 13:48:08 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 51066 invoked by uid 99); 15 May 2017 13:48:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2017 13:48:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C25651AFD46 for ; Mon, 15 May 2017 13:48:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id GCq69awbC84P for ; Mon, 15 May 2017 13:48:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CA6EB5FE2E for ; Mon, 15 May 2017 13:48:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 27C2EE0D8C for ; Mon, 15 May 2017 13:48:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 51A3B24329 for ; Mon, 15 May 2017 13:48:04 +0000 (UTC) Date: Mon, 15 May 2017 13:48:04 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSTUDIO-1132) CN=CONFIGURATION entry on IBM Directory server shows no content MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 15 May 2017 13:48:10 -0000 [ https://issues.apache.org/jira/browse/DIRSTUDIO-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010536#comment-16010536 ] Emmanuel Lecharny commented on DIRSTUDIO-1132: ---------------------------------------------- Hi Pekka, can you try with {{cn=configuration}} instead of {{CN=CONFIGURATION}} ? > CN=CONFIGURATION entry on IBM Directory server shows no content > --------------------------------------------------------------- > > Key: DIRSTUDIO-1132 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1132 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser > Affects Versions: 2.0.0-M9 (2.0.0.v20150606-M9), 2.0.0-M10 (2.0.0.v20151221-M10), 2.0.0-M12 > Environment: Windows 7, Windows 8.1, Windows 10. IBM Directory server versions v6.0, v6.3.0, v6.3.1, v6.4, v8.0 > Reporter: Cristian Horacio Ares > Priority: Minor > Labels: apacheDS, browser, bug, ibm, issue, ldap > > When trying to browse the container entries inside CN=CONFIGURATION entry (and itself) on an IBM Directory server (IBM LDAP), it shows no content, where it should be the full configuration settings of the directory server, with their corresponding objectclasses and attributes. > Testing this through java based ldap browser (gawor ldap browser), web-based ldap browsers and ldapadmin, they are able to see the contents. -- This message was sent by Atlassian JIRA (v6.3.15#6346)