>From the "for what it may be worth" department... University of Arkansas is relying heavily on LDAP authentication for a number of production UNIX systems (Solaris and Linux), as well as application-level user authentication. Setting up the S/390 Red Hat Linux build to defer to an external LDAP via PAM was a trivial exercise, no different than configuring PAM/LDAP on Lintel gear.
The LDAP back end supporting this work is Sun/iPlanet Directory Server. The Solaris systems are using locally compiled open source code from www.padl.com. The Red Hat systems are using - I believe - the same code, already co-packed with RHL. -dan. On Fri, 14 Feb 2003, Joe Poole wrote: > Steve; > > I have the z/OS LDAP server running, with both TDBM (DB2) and SDBM > (RACF) databases gen'd. It looks promising, in that I'm using batch > (IKJEFT01) to experiment with different RACF and DB2 calls. Other > priorities have not allowed us the opportunity to test with z/Linux, > but the Red Book makes it look easy - "Securing Linux for zSeries > with a Central z/OS (RACF) LDAP Server. Also, you'll need SC24-5923 > for Administration and Use. Follow the procedures in both books > simultaneously, since they complement one another very well. Maybe I > can get back to it once the auditors leave. (sigh) > > JP > > On Friday 14 February 2003 13:13, you wrote: > I'm interested in opinions and experience of others to provide > centralized login, passwd, and su authorizations using Linux-PAM > and LDAP and RACF or some other central database. That is, with > mulitple Linux servers, I want to use a central database (RACF, > LDAP, whatever) to store/maintain login and password data. > > Steve Collins IGS [EMAIL PROTECTED] >
