Login and case sensitivity

[ngcutura]

I saw some issues like this on this forum but no replies. Here is another one:

I have Alfresco Labs 3.0 on Windows server, authentication is passthrough against existing Windows domain.
When I use FF 3.0, browser based login occurs - a window is presented and when I enter SomeUser/SomePass, Alfresco logs me in as SomeUser (this is displayed in the upper row).

However, when I use FF 3.5. form based (sic!) login occurs - a form is presented like when the browser is not recognized (FF 3.5 is younger than Alfresco 3.0 but I thought that any FF is recognized as FF by any Alfresco) - and when I enter SomeUser/SomePass, Alfresco logs me in as someuser (this is displayed in the upper window - could it be that the form lowers the case of username?).

Both 'someuser' and 'SomeUser' exist in Alfresco ('ShowAllUsers' shows both) and if they both participate in the same project, things get complicated (like they don't see their sandboxes). In this situation, I tried to restart Alfresco and it stopped, but couldn't start due to 'duplicate root entry in avm://someproject/someuser store'. I had to manually hack Derby DB and then I recreated all indices as explained in a relevant issue and Alfresco is now up and running

BUT

I can't prevent users from using FF 3.5 and FF 3.0 and entering mixed case username - and that means that I am in a big trouble… 😞

Any thoughts? Any help is very precious to me.

Thanks and regards,
NGC

[dward]

I have logged

https://issues.alfresco.com/jira/browse/ETHREEOH-2661

Regards

Dave

[dward]

Just to give an update on this. The problem came down to Alfresco 3.0's behaviour on a case sensitive DB such as Derby as opposed to a case insensitive one such as MySQL.

In v3.2 there is a flag to control the case sensitivity of usernames

user.name.caseSensitive

If you leave it as false, you won't have any problems with user name case sensitivity. And it has been fixed to work regardless of the database's case sensitivity.

On 3.0 user ID matching only worked in case sensitive mode on a case sensitive database and you would have to set user.name.caseSensitive=true.

[archimadhu86]

Not working for me