we have tried it with the following..
IE6 and 7 on windows
IE6 on linux (using ie4linux and wine)
Firefox 2.0.12 on windows and on linux
all behave the same..
all the tools we have to get information out from the ldap gives us the
username out in utf-8 correctly so for me it looks like it is s
ofcourse, it would be better, but unfourtunally it is not up to me to
enforce this policy, and we already have a lot of users with those
character in both username and/or password..
we had the system up and running before but after switching the website
over from ISO-8859-1 to UTF-8 it i sno l
I think that better is for userID and passwords don't use national
characters. In Latvia we time after time have similar problems ...
Andris Eiduks
On Fri, Feb 29, 2008 at 9:53 AM, Antonio Petrelli <
[EMAIL PROTECTED]> wrote:
> 2008/2/20, Christian Andersson <[EMAIL PROTECTED]>:
> > all our htm
2008/2/20, Christian Andersson <[EMAIL PROTECTED]>:
> all our html pages uses the utf-8 encoding, using slapcat and looking at
> the content the data inside openldap seems to be using utf-8 (the output
> from slapcat is at least utf-8,but I don't know if slapcat converts
> anything)
This might
anyone ?
Christian Andersson skrev:
Hi, we have setup Tomcat (6.0.10) to authenticate using form
authentication against openldap (2.3.27) with the jndirealm and
everything works alright except one little bit of a problem.
if the user name has national characters in it (åæø for norwegian) or
Hi, we have setup Tomcat (6.0.10) to authenticate using form
authentication against openldap (2.3.27) with the jndirealm and
everything works alright except one little bit of a problem.
if the user name has national characters in it (åæø for norwegian) or
the password does, the user cannot aut
