summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorArthur de Jong <arthur@arthurdejong.org>2007-08-19 13:28:33 +0000
committerArthur de Jong <arthur@arthurdejong.org>2007-08-19 13:28:33 +0000
commit45c532c3d7326803f36ed68d4dba437b7c9adc58 (patch)
treed6e41016400ef52429f0c44f58601b01bb322c6e /README
parent02b288faf5f17c0b817578fd690ed2f9467b5bee (diff)
add a note about case-sensitivity of NSS and LDAP databases
git-svn-id: http://arthurdejong.org/svn/nss-pam-ldapd/nss-ldapd@354 ef36b2f9-881f-0410-afb5-c4e39611909c
Diffstat (limited to 'README')
-rw-r--r--README9
1 files changed, 9 insertions, 0 deletions
diff --git a/README b/README
index 8c2fda7..5d713ad 100644
--- a/README
+++ b/README
@@ -287,3 +287,12 @@ When using Microsoft Active Directory server (typically on Microsoft Windows
2000) some changes need to be made to the nss-ldapd.conf configuration file.
The default configuration file has some commented out attribute mappings for
such a setup.
+
+MISC NOTES
+==========
+
+Most values in the NSS databases are considered case-sensitive (e.g. the user
+"Foo" is a different user from "foo"). Values in an LDAP database are however
+case-insensitive. This may cause problems in some corner cases, especially
+when nscd is used for caching. For example when doing a lookup for the user
+"Foo" the user "foo" will be returned if it exists in the database.