• Type: Bug Report
• Resolution: Won't Fix
• Priority: L2 - Critical
• Fix Version/s: None
• Affects Version/s: 7.2.0
• Component/s: admin, tasklist
• Labels:

  • login
• Environment:

  Server: Linux Centos, Tomcat 7, Camunda Standalone Webapp (war)
  LDAP Server: Microsoft Active Directory
  Browser: Google Chrome (on Windows Server 64 bit)

This is the controller panel for Smart Panels app

[CAM-3755] LDAP Authentication fails if password has special (acceented) characters

Collapse comment: Daniel Meyer added a comment - 21/Apr/15 1:44 PM

Daniel Meyer added a comment - 21/Apr/15 1:44 PM

Thanks for reporting this bug.

Expand comment: Daniel Meyer added a comment - 21/Apr/15 1:44 PM

Daniel Meyer added a comment - 21/Apr/15 1:44 PM Thanks for reporting this bug.

Collapse comment: Giorgio added a comment - 21/Apr/15 1:56 PM, Edited by Giorgio - 21/Apr/15 1:57 PM

Giorgio added a comment - 21/Apr/15 1:56 PM - edited

Thanks to you! I noticed that the bug is correlated to Microsoft Active Directory. If I connect to Open Ldap the authentication is ok also with accented characters.

Expand comment: Giorgio added a comment - 21/Apr/15 1:56 PM, Edited by Giorgio - 21/Apr/15 1:57 PM

Giorgio added a comment - 21/Apr/15 1:56 PM - edited Thanks to you! I noticed that the bug is correlated to Microsoft Active Directory. If I connect to Open Ldap the authentication is ok also with accented characters.

Collapse comment: Daniel Meyer added a comment - 21/Apr/15 3:03 PM

Daniel Meyer added a comment - 21/Apr/15 3:03 PM

Thanks for that information. We hope we can look at the issue after the next minor release (7.3)

Let us know if you need assistence with a pull request in case you want to look into it yourself

Expand comment: Daniel Meyer added a comment - 21/Apr/15 3:03 PM

Daniel Meyer added a comment - 21/Apr/15 3:03 PM Thanks for that information. We hope we can look at the issue after the next minor release (7.3) Let us know if you need assistence with a pull request in case you want to look into it yourself

Collapse comment: Stefan added a comment - 20/Jul/15 12:59 PM

Stefan added a comment - 20/Jul/15 12:59 PM

Hi gio.chiriaco,

I have a guess what the problem is. I guess that the credentials would need to be encoded in UTF-8.
Would it be possible that you test this sugestion by encoding the inputs in UTF-8?

Cheers,

Stefan

Expand comment: Stefan added a comment - 20/Jul/15 12:59 PM

Stefan added a comment - 20/Jul/15 12:59 PM Hi gio.chiriaco , I have a guess what the problem is. I guess that the credentials would need to be encoded in UTF-8. Would it be possible that you test this sugestion by encoding the inputs in UTF-8? Cheers, Stefan

Collapse comment: Giorgio added a comment - 20/Jul/15 2:31 PM

Giorgio added a comment - 20/Jul/15 2:31 PM

Hi Stefan,
I added the "org.springframework.web.filter.CharacterEncodingFilter" in web.xml of the camunda web app and "URIEncoding='UTF-8'" to connector configuration in Tomcat.
The same configuration with Open Ldap works, so I think that the problem is related to Active Directory.

Cheers,
Giorgio

Expand comment: Giorgio added a comment - 20/Jul/15 2:31 PM

Giorgio added a comment - 20/Jul/15 2:31 PM Hi Stefan, I added the "org.springframework.web.filter.CharacterEncodingFilter" in web.xml of the camunda web app and "URIEncoding='UTF-8'" to connector configuration in Tomcat. The same configuration with Open Ldap works, so I think that the problem is related to Active Directory. Cheers, Giorgio

Collapse comment: Stefan added a comment - 20/Jul/15 4:05 PM, Edited by Stefan - 20/Jul/15 4:06 PM

Stefan added a comment - 20/Jul/15 4:05 PM - edited

Hi Giorgio,

as you have stated, the problem lies within the Microsoft AD and the question is if there is something we need to change in the platform to get it working if the problem is not on our side.

There are also other people with the same problem:

http://forums.juniper.net/t5/SSL-VPN/Issues-with-surnames-passwords-containing-accents/td-p/36715

Their idea was to tcpdump the connection and checking which encoding the AD wants to be authenticated with.

e.g: you could test Windows-1252 instead of UTF-8

Cheers,

Stefan

Expand comment: Stefan added a comment - 20/Jul/15 4:05 PM, Edited by Stefan - 20/Jul/15 4:06 PM

Stefan added a comment - 20/Jul/15 4:05 PM - edited Hi Giorgio, as you have stated, the problem lies within the Microsoft AD and the question is if there is something we need to change in the platform to get it working if the problem is not on our side. There are also other people with the same problem: http://forums.juniper.net/t5/SSL-VPN/Issues-with-surnames-passwords-containing-accents/td-p/36715 Their idea was to tcpdump the connection and checking which encoding the AD wants to be authenticated with. e.g: you could test Windows-1252 instead of UTF-8 Cheers, Stefan

Collapse comment: Thorben Lindhauer added a comment - 30/Aug/22 3:49 PM

Thorben Lindhauer added a comment - 30/Aug/22 3:49 PM

We are closing this ticket as part of our backlog grooming. Reasons:

• We did not receive sufficient evidence that this ticket is important

Expand comment: Thorben Lindhauer added a comment - 30/Aug/22 3:49 PM

Thorben Lindhauer added a comment - 30/Aug/22 3:49 PM We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important