[ https://issues.apache.org/jira/browse/DIRSTUDIO-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720243#comment-16720243 ]
Jooi Lim commented on DIRSTUDIO-1201: ------------------------------------- Yes, I was getting the error when testing the connection. If "Read-Only" flag is not checked, the connection fails. If I checked it, it works. This is on version 2.0.0.v20180909-M14. As you wrote above, this appears to be a bug. However, we are making connections to 2 LDAP servers as data for users are contained in both servers (one set of users are on server 1, and another set on server 2). Connection to Server 1 never has any issues. But server 2, absent of checking "read-only" flag, it will fail. But as you said it is a bug and looking at the source for isReadOnly, I see what you mean that it is only handled within Studio. Strangely, when I programmatically connect to the first server, it always works but second server always fail using the same credentials. But using the same credentials and another LDAP Windows client (Softerra LDAP Browser 4.5), it works. Programmatically, I am using 1.0.0-RC2. I see there's a newer version now. I'll try that. Coincidently, I also tried using Perl Net::LDAP and it too fails on the 2nd server. This may very well has something to do with the 2nd server configuration. Only thing is using the Softerra LDAP Browser 4.5, and same credentials, one can browse it. > How does checking the "read-only" flag change the connection/authentication > bind? > --------------------------------------------------------------------------------- > > Key: DIRSTUDIO-1201 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1201 > Project: Directory Studio > Issue Type: Question > Components: studio-connection > Affects Versions: 2.0.0-M12 > Reporter: Jooi Lim > Priority: Minor > Attachments: testldap_apachestudio.jpg > > > In the Connection dialog box, there's an option for "read-only". On a LDAP > server that I was trying to connect to, if this "read-only" is not checked, > the connection failed with -49 invalid credentials. > I'm trying to understand programmatically where/how this is done when using > the Apache Directory API. > Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)