dynogreg / openipam

Automatically exported from code.google.com/p/openipam
0 stars 0 forks source link

Make user:search case-insensitive #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Problem:

In Manage Hosts, when searching by user:Username in the search box, users
expect the search to be case-insensitive and are confused when there are no
results for someone they know owns hosts.

Fix:

Since there is likely no convincing case for mixed-case usernames,
especially a use case without confusion, go all the way and make openIPAM
generally case-insensitive with usernames. This will need to change in the
DBBaseInterface get_users() function (and possibly get_hosts()). Also,
modify the backend add_user function to fail on creation of a user who has
the same username as an already created user.

Additional information:

Find a good way to deal with sources of users, whether they are from LDAP,
internal, or some other source.

Original issue reported on code.google.com by fotinaki...@gmail.com on 27 Jan 2009 at 2:30

GoogleCodeExporter commented 9 years ago
Database constraints have been added on our db to prevent upper/lower 
conflicts. 
get_users and get_groups have both been modified to be case-insensitive for 
names.

Usernames are still allowed to have whatever case is desired, and that is 
stored in
the database, but anywhere a comparison is done it is done with lower(username) 
(same
for group names).

Our database schema on our database is out of sync with our schema in the repo. 
 We
should probably go through and find the differences sometime.

I'm not sure what was meant by 'Find a good way to deal with sources of users,
whether they are from LDAP, internal, or some other source." means.  Currently, 
the
DB won't let a username be duplicated, even if it might be from multiple 
sources.  Is
that what you are referring to?  If so, it should probably go in a different 
ticket.

Original comment by ekoyle@gmail.com on 30 Jan 2009 at 9:52