I'm having some trouble moving to 'Self Registration' mode for my LDAP integrated Contour. The problem is that when a user self-registers, Contour doesn't use the exact name that they typed; instead it seems to use whatever mixed case variant of their name exists in Active Directory. The problem is made worse in that AD/LDAP authentication is not case sensitive for usernames, but Contour is.
So that brings us to a situation where our users are successful in self registering for an account, but then they can't login.
Am I understanding the limitations correctly? Is Contour suppose to be case sensitive when matching usernames? Is there any way to a) make Contour case insensitive for usernames, or b) force lower case usernames on account creation (during self registration)? Any other workarounds that anyone can think of?
thanks in advance,
Dan Anolik
We have several customers using LDAP with Contour and you are the second to report this issue. Unfortunately we have not figured what is going on yet. We know Contour is not case sensitive and LDAP should not be case sensitive. While we do store the uid from LDAP as the user name in Contour, letter case does not prevent Contour from finding a user at login. The issue may be that Contour passes along whatever was typed in by the user when they are logging in to LDAP, not the user name as it is stored within Contour's database. The LDAP server should not be case sensitive, but it appears that in your situation the integration is case sensitive.
I've passed your issue to the development team and we'll let you know what we find out.
Steve
Hi Steve,
Thanks for the update. I just did some more testing and verified the following:
So if Contour usernames aren't case sensitive for you, but they are case sensitive for me, then this might have something to do with the database type or database configuration. I'm using Oracle. Do you have an Oracle environment to run a quick username/case test against?
thanks,
Dan
Ah yes, it does seem Oracle is case sensitive. Thanks for the help troubleshooting. We will log this and get it fixed.
This has been fixed in the 2.9.5 release of Contour.
Steve
