In article <rQ30g.497$sd1.259@prv-forum2.provo.novell.com>,
jim@DOT.willeke.com says...
> PAM_LDAP and NSS_LDAP should do the job.
> You could also use the FAN-OUT driver, but it is one-way (to Solaris)
> and populates the traditional "files" on Solaris. I usually fond the
> FAN-OUT driver overkill for one type of implementation.
>
> Solaris provides their own version of PAM/NSS however, it does nto work
> well with eDirectory due to some quirks. You could sync (using LDAP
> Driver) to SunDirectory (Comes with Solaris) and then implement
> Solaris's PAM/NSS.
>
> However, if you have any other *in*x in your environment I have found it
> best to use (compile) the PADL (http://www.padl.com/) libraries using
> the JLDAP libraries (SUN uses the old Netscape LDAP libs) on Solaris as
> these same libraries come on most Linux distros and also HP-UX.
> This way, you can use the same config files for all platforms instead of
> managing config files for each. PADL also has code for AIX and others.
>
> -jim
>
>


Thanks everyone for the options.

I'll show these to the Solaris guys and see if they understand it.

(PAM and other cooking sprays--haha)

I had a feeling we would be doing LDAP drivers to an ldap server on
their end somewhere.

--Kevin

>
> Kevin Hurni wrote:
> > Okay, so Sun is getting rid of NIS/NIS+
> >
> > We want to sync from eDir to Solaris
> >
> > I'm guessing that since NIS is going away, we'll want to use the LDAP
> > driver?
> >
> > How is anyone else out there handling syncing to Solaris?
> >
> > Any suggestions/ideas?
> >
> > (I already asked about installing eDir onto Solaris and got a "no we
> > don't want to do that")
> >
> > --Kevin

> http://www.padl.com/
>