Alternative algorithm for finding a user’s DN  Pluggable Authentication Module (PAM) support

Chapter 7: Security Changes

New options added to sp_ldapadmin

The following new options have been added to sp_ldapadmin to support the new DN search algorithm:

For example:

sp_ldapadmin set_access_acct, "cn=admin,
ou=People, dc=mycompany, dc=com", "admin_password"

sp_ldapadmin set_dn_lookup_url,
"ldap://myhost:398/ou=People,dc=mycompany,
dc=com?entrydn?sub?uid=*"

sp_ldapadmin set_primary_url, "ldap://myhost:389/"

For a complete description of sp_ldapadmin, see Chapter 12, “Changes to Global Variables, Commands, and Stored Procedures.”

This example uses the default Microsoft Active Directory schema found on Windows 2000 controllers.

1> sp_ldapadmin set_access_acct, 'cn=aseadmin, cn=Users, dc=mycompany, dc=com', aseadmin secret password
2> go
1> sp_ldapadmin set_dn_lookup_url, 
'ldap://mydomainhostname:389/cn=Users,dc=mycompany,
dc=com?distinguishedName?sub?samaccountname=*' 
2> go
1> sp_ldapadmin set_primary_url,ldap://mydomainhostname:389/
2> go

The “aseadmin” user name has been added to the Active Directory server and granted read access to the trees and objects where users are found. The LDAP attribute specified by “distinguishedName” is obtained and used to authenticate the user. The filter specifies a search on attribute “samaccountname=*”; the * wildcard is replaced with the name from the Adaptive Server login record.

For example, “samaccountname=jqpublic” returns DN attribute “distinguishedName” with value “cn=John Q. Public, cn=Users,dc=mycompany, dc=com” to Adaptive Server. Adaptive Server uses this string to bind to ldap://mydomainhostname:389. If the bind is successful, authentication succeeds.





Copyright © 2004. Sybase Inc. All rights reserved. Pluggable Authentication Module (PAM) support

View this book as PDF