Problem with LDAP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-05-2007 04:54 PM
Hey,
I have recently inherited the task of maintaining an Alfresco 1.4 installation from a co-worker. Users were receiving an error when the logged in and I tracked the issue to be related to a case-insensitive table in mysql. My understanding is that the user was logged in as 'jenglert' bu the user's home space was owned by 'JEnglert'. Thus, the user did not have sufficient privileges to browse their home space and an error resulted. I updated the table to be case sensitive as well as set the flag in 'repository.properties'. Users could now successfully log in. The only remaining issue is that each space seems to be owned by two versions of the same user. (See the attached picture.)
[img]http://i157.photobucket.com/albums/t71/jenglret/twousers.gif[/img]
Has any experienced an error like this before? Thanks in advance for your input.
Thanks!
I have recently inherited the task of maintaining an Alfresco 1.4 installation from a co-worker. Users were receiving an error when the logged in and I tracked the issue to be related to a case-insensitive table in mysql. My understanding is that the user was logged in as 'jenglert' bu the user's home space was owned by 'JEnglert'. Thus, the user did not have sufficient privileges to browse their home space and an error resulted. I updated the table to be case sensitive as well as set the flag in 'repository.properties'. Users could now successfully log in. The only remaining issue is that each space seems to be owned by two versions of the same user. (See the attached picture.)
[img]http://i157.photobucket.com/albums/t71/jenglret/twousers.gif[/img]
Has any experienced an error like this before? Thanks in advance for your input.
Thanks!
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2007 11:28 AM
Hi
Setting user names to be case sensitive in repository.properties is never the issue.
How are you authenticating?
There was a bug in 1.4.0 community where the NTLM filters always transformed the user names to lower case.
What should happen is …. LDAP imports users with whatever case is in your ldap store. When you authenticate via NTLM it authenticates regardless of case - and the user names is set to the case sensitve value imported. If NTLM authenticates and the person os not found it can create missing people - it will create them lower case - then the LDAP import will find them and update everything - includig the user name. The hooks are not there at the moment to update the permission assigments if this happensl. It is simple to avoid if you turn off autocreating people in authentication-services-context.xml.
Regards
Andy
Setting user names to be case sensitive in repository.properties is never the issue.
How are you authenticating?
There was a bug in 1.4.0 community where the NTLM filters always transformed the user names to lower case.
What should happen is …. LDAP imports users with whatever case is in your ldap store. When you authenticate via NTLM it authenticates regardless of case - and the user names is set to the case sensitve value imported. If NTLM authenticates and the person os not found it can create missing people - it will create them lower case - then the LDAP import will find them and update everything - includig the user name. The hooks are not there at the moment to update the permission assigments if this happensl. It is simple to avoid if you turn off autocreating people in authentication-services-context.xml.
Regards
Andy
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2007 01:57 PM
Thanks for the quick response. Using your solutions, we were able to remedy the situation.
The only remaining question I have is how can I effectively tell which version of the code I am using. When I go to the Administration Console->System Information->Repository Properties->Server Version the version is 1.4.0 (@build-number@). I assume this means he pulled the source from SVN when he made his customizations. The instance says 'Enterprise Edition' at the bottom though, how is this possible?
Thanks again!
The only remaining question I have is how can I effectively tell which version of the code I am using. When I go to the Administration Console->System Information->Repository Properties->Server Version the version is 1.4.0 (@build-number@). I assume this means he pulled the source from SVN when he made his customizations. The instance says 'Enterprise Edition' at the bottom though, how is this possible?
Thanks again!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2007 06:21 AM
Hi
This means you have built your own version of 1.4.0 enterprise - which is perfectly fine. That is why there is no build number.
Andy
This means you have built your own version of 1.4.0 enterprise - which is perfectly fine. That is why there is no build number.
Andy
