Secure Global Desktop 4.40 Administration Guide > Users and Authentication > LDAP Users Cannot Log in to SGD
If you are using LDAP authentication and you find that LDAP users cannot log in to SGD, use the following checklist to identify the source of the problem. If this does not resolve the problem, use the following log filters:
server/login/* filter allows you see what happens what LDAP users attempt to log in . The
server/ldap/* filter allows you to see errors with connections to the LDAP directory.
|Things to check||Notes|
|Is LDAP authentication enabled?||You cannot use an LDAP directory server with SGD unless the LDAP authentication is enabled.|
|Are the URLs of the LDAP directory servers correct?||To be able to use LDAP authentication, each SGD server must be
able to contact the LDAP directory servers at the specified URLs.
Check the URLs:
For Sun™ ONE (formerly Netscape or iPlanet) Directory Server, you might also need to do
some extra configuration to map names in the local repository to LDAP names correctly.
For example, the LDAP directory has a
|Is the LDAP directory server user name and password correct?||Some LDAP directory servers support anonymous logins, so you do not need to supply a user name or password. Others, including Microsoft Active Directory, require the user name and password of a user that has sufficient privileges to search the LDAP directory.|
|If you are you using secure connections to the LDAP directory server, has this been configured correctly?||
See Securing connections to LDAP directory servers for details.
|Is SGD providing the right information for locating the user?||When SGD searches an LDAP directory for a user it uses the following attributes:
If these attributes are not sufficient for identifying users, you can add extra attributes as follows:
Note These steps require caution as any mistakes can result in all users being unable to log in.
|Have recent LDAP configuration changes taken effect?||After making changes to your LDAP database, it is advisable to wait for a period of time for the changes to take effect.
SGD caches the data it collects from an LDAP directory. If you find that SGD is not detecting changes, you can manually flush the cached data with the
Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.