ldap_integration
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ldap_integration [2009/08/20 09:19] – 172.26.0.166 | ldap_integration [2009/08/21 06:39] – 172.26.0.166 | ||
---|---|---|---|
Line 3: | Line 3: | ||
ILRI uses an Active Directory server for user authentication, | ILRI uses an Active Directory server for user authentication, | ||
- | ==== Notes ==== | + | ===== Notes ===== |
+ | |||
+ | ==== Using ldapsearch on Linux ==== | ||
Try to search from a Linux machine which can talk to the AD server (HPC is behind firewall): | Try to search from a Linux machine which can talk to the AD server (HPC is behind firewall): | ||
+ | < | ||
+ | |||
< | < | ||
Enter LDAP Password: | Enter LDAP Password: | ||
Line 13: | Line 17: | ||
DEC: 1317 – ERROR_NO_SUCH_USER (The specified account does not exist.) | DEC: 1317 – ERROR_NO_SUCH_USER (The specified account does not exist.) | ||
NOTE: Returns when username is invalid.</ | NOTE: Returns when username is invalid.</ | ||
- | Note from [[http:// | + | ==== binddn ==== |
- | < | + | A note of possible interest regarding binding on Linux (from the [[http:// |
- | only accept binds on that port. You cannot bind as a user on port 389. I | + | < |
- | don't think they support TLS on port 389, but I have no tried in a long | + | You cannot bind as a user on port 389. I don't think they support TLS on port 389, but I have no tried in a |
- | time.</ | + | long time.</ |
- | + | ==== Domain controller vs. Global catalog | |
- | ==== pam_cgiar_ldap.c ==== | + | As ILRI has many AD domains and our users could be coming from anywhere, we need to query a server running the global catalog service instead of a normal domain controller. |
+ | < | ||
+ | on the standard LDAP port 389. However, domain controllers (including Global Catalog Servers) respond to LDAP | ||
+ | | ||
+ | | ||
+ | requests on port 3268, Microsoft' | ||
+ | with AD information from the entire AD forest. In multi-domain AD environments, | ||
+ | ILRI Kenya has three Active Directory servers, and from what I can tell two of them run a global catalog: | ||
+ | * 172.26.0.218 <- running a global catalog (port 3268) | ||
+ | * 172.26.0.219 | ||
+ | * 172.26.0.220 <- running a global catalog (port 3268) | ||
+ | ===== pam_cgiar_ldap.c ===== | ||
+ | Someone hacked up a PAM module several years ago which could be dropped into a Linux server and allow AD authentication with minimal configuration. | ||
<note warning> | <note warning> | ||
This was working once, using a // | This was working once, using a // | ||
* Compile the code: '' | * Compile the code: '' | ||
- | * Link the code: '' | + | * Link the code: '' |
**pam_cgiar_ldap.c**: | **pam_cgiar_ldap.c**: |
ldap_integration.txt · Last modified: 2012/02/06 08:43 by aorth