User Tools

Site Tools


ldap_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
ldap_integration [2009/08/14 09:41] aorthldap_integration [2009/08/17 07:26] – external edit 127.0.0.1
Line 3: Line 3:
 ILRI uses an Active Directory server for user authentication, which is primarily used for Exchange e-mail services.  Currently users have an Active Directory username and password for their Windows-centric single sign on and e-mail, and then they have a separate account for use with the HPC.  There exists functionality in Linux to look at Active Directory for user authentication. ILRI uses an Active Directory server for user authentication, which is primarily used for Exchange e-mail services.  Currently users have an Active Directory username and password for their Windows-centric single sign on and e-mail, and then they have a separate account for use with the HPC.  There exists functionality in Linux to look at Active Directory for user authentication.
  
-This was working once, using a //slightly// customized PAM module.  The source code for pam_cgiar_ldap.c is below:+This was working once, using a //slightly// customized PAM module.  In order to use the module several steps are needed.  Download the module source and compile it as shown below: 
 +  * Compile the code:  ''gcc -fPIC  -c pam_cgiar_ldap.c'' 
 +  * Link the code ''ld -x --shared -o pam_cgiar_ldap.so pam_cgiar_ldap.o –lldap''
  
 +**pam_cgiar_ldap.c**:
 <code c> <code c>
 #define DEFAULT_USER "nobody" #define DEFAULT_USER "nobody"
ldap_integration.txt · Last modified: 2012/02/06 08:43 by aorth