Slackware and centralized authentication?

Hi,

I've been using Slackware for a few years, between 2001 and 2006 or so,
before switching to a personal mix of CentOS and Fedora, for reasons
mostly due to work. After that, I've used various blends of distros. But
Slackware has been my first lov^^^^^ Linux distro.

Lately I've observed a tendency to loss of quality in nearly every
distro around (no names). Since I'm running a small IT company based
exclusively on GNU/Linux and FOSS (http://www.microlinux.fr), this is an
annoyance. Now I'm seriously pondering returning to Slackware, the more
so since I recently decided to take the plunge from GNOME to KDE (after
having used KDE 2.x and KDE 3.x for a few years on Slackware). In my
humble experience, I've encountered only a handful of really *clean*
distros where everything JustWorks(tm): Slackware, CentOS, Pardus and
Gentoo. The CentOS folks are obviously busy rewriting the kernel before
releasing 6.0, Gentoo needs at least a Phantom Jet to build applications
in reasonable time, and unfortunately, I don't speak enough turkish to
grasp what's being said in the Pardus forums. Which leaves Slackware :o)

I'm wondering how central authentication can be done with Slackware, if
it's used on both server and clients. As an example, I've setup recently
a network consisting of one server and twenty client PCs, all running
CentOS, in a private school here. The /home directory is shared with
NFS, and then I'm using the - antique but simple - NIS system for
authentication. Works nice.

Is there any way to have a similar setup with Slackware, without having
to jump through burning loops ?

Cheers from the sunny South of France,

Niki Kovacs