From dev-return-56998-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Dec 27 18:52:07 2017 Return-Path: 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 7EB80173A0 for ; Wed, 27 Dec 2017 18:52:07 +0000 (UTC) Received: (qmail 19309 invoked by uid 500); 27 Dec 2017 18:52:07 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 19255 invoked by uid 500); 27 Dec 2017 18:52:07 -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 19245 invoked by uid 99); 27 Dec 2017 18:52:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Dec 2017 18:52:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D822BC546D for ; Wed, 27 Dec 2017 18:52:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 6ydE-DfaMMqs for ; Wed, 27 Dec 2017 18:52: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 0E9D35F3B6 for ; Wed, 27 Dec 2017 18:52:06 +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 2AF3FE08C2 for ; Wed, 27 Dec 2017 18:52:04 +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 9CC75240DE for ; Wed, 27 Dec 2017 18:52:02 +0000 (UTC) Date: Wed, 27 Dec 2017 18:52:02 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-2215) LDAP: Error 50 - Insufficient Access Rights MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304731#comment-16304731 ] Emmanuel Lecharny commented on DIRSERVER-2215: ---------------------------------------------- Apache Directory Studio is *not* a LDAP server, it's a LDAP browser. Are you using the embeded LDAP server ? > LDAP: Error 50 - Insufficient Access Rights > ------------------------------------------- > > Key: DIRSERVER-2215 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2215 > Project: Directory ApacheDS > Issue Type: Bug > Components: ldap > Affects Versions: 2.0.0-M23 > Environment: windows server 2012 > Reporter: taher fares > Priority: Critical > > hello all, > I have apache Directory studio(LDAP) connected with our mobile application by IBM mobile first (MFP), I have a problem that repeated more than once, LDAP suddenly does not respond to any command from MFP such like Delete and Modify of structure or person/group objects - ALL functions are causing an error and whene i trying to apply any LDIF files the following error appears in the LOG file "apache ldap error code 50 insufficient access rights", > Because of this we have lost many users so I hope you will cooperate to solve this issue as soon as possible > thank you in advance -- This message was sent by Atlassian JIRA (v6.4.14#64029)