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 08:31] – 172.26.0.166 | ldap_integration [2009/08/20 09:19] – 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, | ||
- | <note warning> | + | ==== Notes ==== |
- | HEX: 0×525 – user not found | + | Try to search from a Linux machine which can talk to the AD server (HPC is behind firewall): |
+ | <code>[aorth@shamba: | ||
+ | Enter LDAP Password: | ||
+ | ldap_bind: Invalid credentials (49) | ||
+ | additional info: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece</ | ||
+ | According to the web this error means the user does not exist. | ||
+ | < | ||
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:// | ||
+ | < | ||
+ | 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 | ||
+ | time.</ | ||
==== pam_cgiar_ldap.c ==== | ==== pam_cgiar_ldap.c ==== |
ldap_integration.txt · Last modified: 2012/02/06 08:43 by aorth