ldap
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
ldap [2009/08/17 06:05] – 172.26.0.166 | ldap [2010/05/22 14:19] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 11: | Line 11: | ||
* Implementation | * Implementation | ||
Authentication on a Linux PC’s is managed by PAM modules (Pluggable Authentication Modules). A special PAM module should be used, configured to test username | Authentication on a Linux PC’s is managed by PAM modules (Pluggable Authentication Modules). A special PAM module should be used, configured to test username | ||
+ | |||
+ | Compiling the sources of the custom LDAP module: | ||
+ | |||
+ | '' | ||
+ | |||
+ | Linking the sources | ||
+ | |||
+ | '' | ||
+ | |||
+ | The library pam_cgiar_ldap.so must be copied where the other PAM modules are saved, that is: | ||
+ | |||
+ | ''/ | ||
+ | |||
+ | on the HPC | ||
+ | |||
+ | ''/ | ||
+ | |||
+ | PAM configuration files for each PAM enabled application we want to work with should be configured. | ||
+ | |||
+ | Remember than when using the pam_cgiar_ldap.so module in the PAM file it cannot be on top of the auth stack. | ||
+ | |||
+ | For example to use LDAP authentication for SSH logins we shall include into the file / | ||
+ | |||
See document: CGIAR-HPC-COP.doc | See document: CGIAR-HPC-COP.doc |