Have a site set up tom auth with winbind.so.
It all works OK.
Exept:
When special char in username I am not able to login if the browser is IE.
Using Crome login succeed.
error when using special char is
PAM: user ‘rune.b\xf8e’ - not authenticated: System error
username should rune.bøe
I don’t know where to start looking for a solution.
I can say the the username/passwd dialog box does not show thos spesial charter either.
httpd.conf has defaultCharset UTF-8 (have tried ISO… as well)
Just type in the character as it’s in the database, i.e., rune.bøe is fine while 'rune.b\xf8e is interpreted as “r u n e . b \ x f 8 e” (without the spaces), i.e., a character string. I’m surprised that Chrome would make that translation as “special characters” in passwords is a GOOD thing to have (and should not be automatically interpreted the way you’re indicating).
Not sure if I made myself understood correctly.
I do type in in rune.bøe as the username with both Chrome and Internet Explorer.
When using Internet Explorer error log say’s
PAM: user ‘rune.b\xf8e’ - not authenticated: System error
When using Chrome, user authenticate without error.
Apache virt server .conf
<Directory “/mnt/www/timer”>
AllowOverride None
Options ExecCGI Indexes
DirectoryIndex index index.php index.html
AuthPam_Enabled On
AuthName “Logg på Timeregistrering”
AuthPAM_FallThrough Off
AuthType Basic
require valid-user
</Directory>
<VirtualHost *:80>
ServerAdmin webmaster@ost.htg.org
DocumentRoot /mnt/www/timer
ServerName timer.helgesen.local
ServerAlias timer
ErrorLog logs/timer-error_log
CustomLog logs/timer-access_log common
</VirtualHost>
Okay, thanks for that clarification. It’s clearly a difference between the way that Chrome and IE handle the charset, i.e., the login page should specifically include the charset which recognizes the ø as a valid character. The simple fact that Chrome does identify it properly is a good indication that Apache is accepting your native charset as well as Chrome. IE obviously defaults to a different charset.
Well I don’ think that the first page has anything to do with it.
As far as I know Apache do not read the page when dealing with directory security. It fires a credential dialog when entering the directory, and therefor charset of index(or requested) page does not come in to action.
I’v tried to change default charset for Apache between UTF8 and ISO-8859-1.
There is no different result.