Uploaded image for project: 'Directory Studio'
  1. Directory Studio
  2. DIRSTUDIO-819

Cannot open entries with DNs with UTF8 characters (Active Directory)

    Details

      Description

      In the LDAPBrowser, after searching for, and finding, the entries in Active Directory, when I try to see the attributes of the entry (selecting the entry), nothing is shown on the right panel.
      This happens only with entries which have UTF8 characters in the DN (for example, names of people in spanish).

        Issue Links

          Activity

          Hide
          pamarcelot Pierre-Arnaud Marcelot added a comment -

          Hi David,

          Do you have any errors showing up somewhere?

          Are you using Apache Directory Studio as standalone application or within Eclipse?

          Can you give an example of a DN it is failing with?

          Thanks,
          Pierre-Arnaud

          Show
          pamarcelot Pierre-Arnaud Marcelot added a comment - Hi David, Do you have any errors showing up somewhere? Are you using Apache Directory Studio as standalone application or within Eclipse? Can you give an example of a DN it is failing with? Thanks, Pierre-Arnaud
          Hide
          dmborque David Martinez Borque added a comment -

          Hi,
          No, I don't get any error.
          I am using Apache Directory Studio as standalone.

          One example:
          The DN of the entry is: CN=Vicerrectorado Posgrado y Formación Continua,OU=Usuarios,DC=pas,DC=ucm,DC=es
          When selecting it, nothing is shown on the right panel (table entry editor). If I choose to open it with "LDIF Entry Editor" the corresponding tab shows:

          dn:: Q049VmljZXJyZWN0b3JhZG8gUG9zZ3JhZG8geSBGb3JtYWNpw7NuIENvbnRpbnVhLE9VPVV
          zdWFyaW9zLERDPXBhcyxEQz11Y20sREM9ZXM=

          and nothing more.

          ¿Could it be some misconfiguration on my side?
          Thanks,
          David

          Show
          dmborque David Martinez Borque added a comment - Hi, No, I don't get any error. I am using Apache Directory Studio as standalone. One example: The DN of the entry is: CN=Vicerrectorado Posgrado y Formación Continua,OU=Usuarios,DC=pas,DC=ucm,DC=es When selecting it, nothing is shown on the right panel (table entry editor). If I choose to open it with "LDIF Entry Editor" the corresponding tab shows: dn:: Q049VmljZXJyZWN0b3JhZG8gUG9zZ3JhZG8geSBGb3JtYWNpw7NuIENvbnRpbnVhLE9VPVV zdWFyaW9zLERDPXBhcyxEQz11Y20sREM9ZXM= and nothing more. ¿Could it be some misconfiguration on my side? Thanks, David
          Hide
          pamarcelot Pierre-Arnaud Marcelot added a comment -

          Ok thanks.

          Could you have a look and post the last entries of the log located here:

          {USER_HOME}

          /.ApacheDirectoryStudio/.metadata/.log ?

          I don't think that's a misconfiguration, probably an interesting bug.

          Thanks

          Show
          pamarcelot Pierre-Arnaud Marcelot added a comment - Ok thanks. Could you have a look and post the last entries of the log located here: {USER_HOME} /.ApacheDirectoryStudio/.metadata/.log ? I don't think that's a misconfiguration, probably an interesting bug. Thanks
          Hide
          dmborque David Martinez Borque added a comment -

          Ok, here's the log of the last two days (nothing relevant, I'm afraid):

          !SESSION 2012-07-05 09:42:52.377 -----------------------------------------------

          eclipse.buildId=unknown

          java.version=1.6.0_33

          java.vendor=Sun Microsystems Inc.

          BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES

          Command-line arguments: -os win32 -ws win32 -arch x86

          !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 13:45:38.392

          !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1

          !SESSION 2012-07-05 13:48:11.445 -----------------------------------------------

          eclipse.buildId=unknown

          java.version=1.6.0_33

          java.vendor=Sun Microsystems Inc.

          BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES

          Command-line arguments: -os win32 -ws win32 -arch x86

          !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 14:18:30.176

          !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1

          !SESSION 2012-07-05 14:36:28.040 -----------------------------------------------

          eclipse.buildId=unknown

          java.version=1.6.0_33

          java.vendor=Sun Microsystems Inc.

          BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES

          Command-line arguments: -os win32 -ws win32 -arch x86

          !ENTRY org.eclipse.update.configurator 4 0 2012-07-05 14:36:30.354

          !MESSAGE Could not install bundle plugins/org.apache.directory.studio.ldifeditor.help_2.0.0.v20120224.jar Bundle "org.apache.directory.studio.ldifeditor.help" version "2.0.0.v20120224" has already been installed from: update@plugins/org.apache.directory.studio.ldifeditor.help_2.0.0.v20120224/

          !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 15:04:51.217

          !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1

          !SESSION 2012-07-06 10:01:56.273 -----------------------------------------------

          eclipse.buildId=unknown

          java.version=1.6.0_33

          java.vendor=Sun Microsystems Inc.

          BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES

          Command-line arguments: -os win32 -ws win32 -arch x86

          !ENTRY org.eclipse.core.jobs 2 2 2012-07-06 10:03:25.785

          !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.update.internal.scheduler.AutomaticUpdateJob

          !SESSION 2012-07-06 10:02:19.068 -----------------------------------------------

          eclipse.buildId=unknown

          java.version=1.6.0_33

          java.vendor=Sun Microsystems Inc.

          BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES

          Command-line arguments: -os win32 -ws win32 -arch x86

          !ENTRY org.eclipse.core.jobs 2 2 2012-07-06 10:45:35.806

          !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1

          Show
          dmborque David Martinez Borque added a comment - Ok, here's the log of the last two days (nothing relevant, I'm afraid): !SESSION 2012-07-05 09:42:52.377 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 13:45:38.392 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 !SESSION 2012-07-05 13:48:11.445 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 14:18:30.176 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 !SESSION 2012-07-05 14:36:28.040 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.update.configurator 4 0 2012-07-05 14:36:30.354 !MESSAGE Could not install bundle plugins/org.apache.directory.studio.ldifeditor.help_2.0.0.v20120224.jar Bundle "org.apache.directory.studio.ldifeditor.help" version "2.0.0.v20120224" has already been installed from: update@plugins/org.apache.directory.studio.ldifeditor.help_2.0.0.v20120224/ !ENTRY org.eclipse.core.jobs 2 2 2012-07-05 15:04:51.217 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1 !SESSION 2012-07-06 10:01:56.273 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.jobs 2 2 2012-07-06 10:03:25.785 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.update.internal.scheduler.AutomaticUpdateJob !SESSION 2012-07-06 10:02:19.068 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_33 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.jobs 2 2 2012-07-06 10:45:35.806 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.apache.directory.studio.common.core.jobs.StudioProgressMonitor$1
          Hide
          pamarcelot Pierre-Arnaud Marcelot added a comment -

          Indeed, no errors so far...

          I will try to reproduce the issue.

          Thanks.

          Show
          pamarcelot Pierre-Arnaud Marcelot added a comment - Indeed, no errors so far... I will try to reproduce the issue. Thanks.
          Hide
          pamarcelot Pierre-Arnaud Marcelot added a comment -

          Hi,

          I created a user with the same name you provided but I haven't been able to reproduce the issue.

          I can open the entry in all editors and all attributes are there...

          Are you sure the user you're using to connect to AD has the required access level to show all attributes?
          Does it work in any other LDAP Browser?
          Could you do an LDIF export of bogus and non bogus users please?

          Thanks!

          Show
          pamarcelot Pierre-Arnaud Marcelot added a comment - Hi, I created a user with the same name you provided but I haven't been able to reproduce the issue. I can open the entry in all editors and all attributes are there... Are you sure the user you're using to connect to AD has the required access level to show all attributes? Does it work in any other LDAP Browser? Could you do an LDIF export of bogus and non bogus users please? Thanks!
          Hide
          bergolth Leo Bergolth added a comment -

          I have the same problem (AD, DN with UTF8 characters).

          The packet dump and even the raw packet data shows that Directory Studio uses (the 6 byte string) "\C3\B6" to search for an "Umlaut o" while it should use an UTF-8 encoded string directly, without quoting. I.e. it should send the two bytes 0xc3 0xb6.

          Here is the Directory Studio search request captured by wireshark:
          ------------------------------------------------------------------------
          No. Time Source Destination Protocol Info
          1 0.000000 172.23.61.103 172.23.3.199 LDAP searchRequest(32) "cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local" singleLevel

          Frame 1: 215 bytes on wire (1720 bits), 215 bytes captured (1720 bits)
          Raw packet data
          Internet Protocol, Src: 172.23.61.103 (172.23.61.103), Dst: 172.23.3.199 (172.23.3.199)
          Transmission Control Protocol, Src Port: 36246 (36246), Dst Port: ldap (389), Seq: 1, Ack: 1, Len: 163
          Lightweight Directory Access Protocol
          LDAPMessage searchRequest(32) "cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local" singleLevel
          messageID: 32
          protocolOp: searchRequest (3)
          searchRequest
          baseObject: cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local
          scope: singleLevel (1)
          derefAliases: derefAlways (3)
          sizeLimit: 1000
          timeLimit: 0
          typesOnly: False
          Filter: (objectClass=*)
          attributes: 1 item
          [Response In: 2]

          No. Time Source Destination Protocol Info
          2 0.008476 172.23.3.199 172.23.61.103 LDAP searchResDone(32) noSuchObject (0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:
          'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local'
          ) [0 results]

          Frame 2: 296 bytes on wire (2368 bits), 296 bytes captured (2368 bits)
          Raw packet data
          Internet Protocol, Src: 172.23.3.199 (172.23.3.199), Dst: 172.23.61.103 (172.23.61.103)
          Transmission Control Protocol, Src Port: ldap (389), Dst Port: 36246 (36246), Seq: 1, Ack: 164, Len: 244
          Lightweight Directory Access Protocol
          LDAPMessage searchResDone(32) noSuchObject (0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:
          'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local'
          ) [0 results]
          messageID: 32
          protocolOp: searchResDone (5)
          searchResDone
          resultCode: noSuchObject (32)
          matchedDN: OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local
          errorMessage: 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:\n\t'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local'\n
          [Response To: 1]
          [Time: 0.008476000 seconds]
          ------------------------------------------------------------------------

          And is the same request using the ldapsearch commandline client: (which works fine)
          ------------------------------------------------------------------------
          No. Time Source Destination Protocol Info
          58 842.819622 172.23.61.103 172.23.3.199 LDAP searchRequest(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" wholeSubtree

          Frame 58: 201 bytes on wire (1608 bits), 201 bytes captured (1608 bits)
          Raw packet data
          Internet Protocol, Src: 172.23.61.103 (172.23.61.103), Dst: 172.23.3.199 (172.23.3.199)
          Transmission Control Protocol, Src Port: 36663 (36663), Dst Port: ldap (389), Seq: 130, Ack: 23, Len: 149
          Lightweight Directory Access Protocol
          LDAPMessage searchRequest(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" wholeSubtree
          messageID: 2
          protocolOp: searchRequest (3)
          searchRequest
          baseObject: CN=Gr\303\266schl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local
          scope: wholeSubtree (2)
          derefAliases: neverDerefAliases (0)
          sizeLimit: 0
          timeLimit: 0
          typesOnly: False
          Filter: (objectclass=*)
          attributes: 1 item
          [Response In: 59]

          No. Time Source Destination Protocol Info
          59 842.827507 172.23.3.199 172.23.61.103 LDAP searchResEntry(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" | searchResDone(2) success [1 result]

          Frame 59: 201 bytes on wire (1608 bits), 201 bytes captured (1608 bits)
          Raw packet data
          Internet Protocol, Src: 172.23.3.199 (172.23.3.199), Dst: 172.23.61.103 (172.23.61.103)
          Transmission Control Protocol, Src Port: ldap (389), Dst Port: 36663 (36663), Seq: 23, Ack: 279, Len: 149
          Lightweight Directory Access Protocol
          LDAPMessage searchResEntry(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" [1 result]
          messageID: 2
          protocolOp: searchResEntry (4)
          searchResEntry
          objectName: CN=Gr\303\266schl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local
          attributes: 0 items
          [Response To: 58]
          [Time: 0.007885000 seconds]
          Lightweight Directory Access Protocol
          LDAPMessage searchResDone(2) success [1 result]
          messageID: 2
          protocolOp: searchResDone (5)
          searchResDone
          resultCode: success (0)
          matchedDN:
          errorMessage:
          [Response To: 58]
          [Time: 0.007885000 seconds]
          ------------------------------------------------------------------------

          Show
          bergolth Leo Bergolth added a comment - I have the same problem (AD, DN with UTF8 characters). The packet dump and even the raw packet data shows that Directory Studio uses (the 6 byte string) "\C3\B6" to search for an "Umlaut o" while it should use an UTF-8 encoded string directly, without quoting. I.e. it should send the two bytes 0xc3 0xb6. Here is the Directory Studio search request captured by wireshark: ------------------------------------------------------------------------ No. Time Source Destination Protocol Info 1 0.000000 172.23.61.103 172.23.3.199 LDAP searchRequest(32) "cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local" singleLevel Frame 1: 215 bytes on wire (1720 bits), 215 bytes captured (1720 bits) Raw packet data Internet Protocol, Src: 172.23.61.103 (172.23.61.103), Dst: 172.23.3.199 (172.23.3.199) Transmission Control Protocol, Src Port: 36246 (36246), Dst Port: ldap (389), Seq: 1, Ack: 1, Len: 163 Lightweight Directory Access Protocol LDAPMessage searchRequest(32) "cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local" singleLevel messageID: 32 protocolOp: searchRequest (3) searchRequest baseObject: cn=Gr\C3\B6schl Christian 6125 (OERK-N KL),ou=User,ou=Klosterneuburg,ou=Dienststellen,dc=noe,dc=arc,dc=local scope: singleLevel (1) derefAliases: derefAlways (3) sizeLimit: 1000 timeLimit: 0 typesOnly: False Filter: (objectClass=*) attributes: 1 item [Response In: 2] No. Time Source Destination Protocol Info 2 0.008476 172.23.3.199 172.23.61.103 LDAP searchResDone(32) noSuchObject (0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local' ) [0 results] Frame 2: 296 bytes on wire (2368 bits), 296 bytes captured (2368 bits) Raw packet data Internet Protocol, Src: 172.23.3.199 (172.23.3.199), Dst: 172.23.61.103 (172.23.61.103) Transmission Control Protocol, Src Port: ldap (389), Dst Port: 36246 (36246), Seq: 1, Ack: 164, Len: 244 Lightweight Directory Access Protocol LDAPMessage searchResDone(32) noSuchObject (0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local' ) [0 results] messageID: 32 protocolOp: searchResDone (5) searchResDone resultCode: noSuchObject (32) matchedDN: OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local errorMessage: 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:\n\t'OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local'\n [Response To: 1] [Time: 0.008476000 seconds] ------------------------------------------------------------------------ And is the same request using the ldapsearch commandline client: (which works fine) ------------------------------------------------------------------------ No. Time Source Destination Protocol Info 58 842.819622 172.23.61.103 172.23.3.199 LDAP searchRequest(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" wholeSubtree Frame 58: 201 bytes on wire (1608 bits), 201 bytes captured (1608 bits) Raw packet data Internet Protocol, Src: 172.23.61.103 (172.23.61.103), Dst: 172.23.3.199 (172.23.3.199) Transmission Control Protocol, Src Port: 36663 (36663), Dst Port: ldap (389), Seq: 130, Ack: 23, Len: 149 Lightweight Directory Access Protocol LDAPMessage searchRequest(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" wholeSubtree messageID: 2 protocolOp: searchRequest (3) searchRequest baseObject: CN=Gr\303\266schl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local scope: wholeSubtree (2) derefAliases: neverDerefAliases (0) sizeLimit: 0 timeLimit: 0 typesOnly: False Filter: (objectclass=*) attributes: 1 item [Response In: 59] No. Time Source Destination Protocol Info 59 842.827507 172.23.3.199 172.23.61.103 LDAP searchResEntry(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" | searchResDone(2) success [1 result] Frame 59: 201 bytes on wire (1608 bits), 201 bytes captured (1608 bits) Raw packet data Internet Protocol, Src: 172.23.3.199 (172.23.3.199), Dst: 172.23.61.103 (172.23.61.103) Transmission Control Protocol, Src Port: ldap (389), Dst Port: 36663 (36663), Seq: 23, Ack: 279, Len: 149 Lightweight Directory Access Protocol LDAPMessage searchResEntry(2) "CN=Gröschl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local" [1 result] messageID: 2 protocolOp: searchResEntry (4) searchResEntry objectName: CN=Gr\303\266schl Christian 6125 (OERK-N KL),OU=User,OU=Klosterneuburg,OU=Dienststellen,DC=noe,DC=arc,DC=local attributes: 0 items [Response To: 58] [Time: 0.007885000 seconds] Lightweight Directory Access Protocol LDAPMessage searchResDone(2) success [1 result] messageID: 2 protocolOp: searchResDone (5) searchResDone resultCode: success (0) matchedDN: errorMessage: [Response To: 58] [Time: 0.007885000 seconds] ------------------------------------------------------------------------
          Hide
          pamarcelot Pierre-Arnaud Marcelot added a comment -

          Hi Leo,

          Is this issue still relevant?

          As we fixed recently issues related to non-ascii characters in DN, I think it might be fixed.

          Thanks in advance.
          Pierre-Arnaud

          Show
          pamarcelot Pierre-Arnaud Marcelot added a comment - Hi Leo, Is this issue still relevant? As we fixed recently issues related to non-ascii characters in DN, I think it might be fixed. Thanks in advance. Pierre-Arnaud
          Hide
          tomasbrixi Tomas Brixi added a comment -

          Hello,

          it seems that the problem remains still at least in ldap modify request.
          Studio version 2.0.0.v20130628

          Show
          tomasbrixi Tomas Brixi added a comment - Hello, it seems that the problem remains still at least in ldap modify request. Studio version 2.0.0.v20130628
          Hide
          seelmann Stefan Seelmann added a comment -

          Fixed, see linked issues.

          Show
          seelmann Stefan Seelmann added a comment - Fixed, see linked issues.

            People

            • Assignee:
              seelmann Stefan Seelmann
              Reporter:
              dmborque David Martinez Borque
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development