389 directory server or openldap

Latest response

Hello,
i'd like to discuss / ask the auditorium here about the possibility of replacement of NIS and Samba.

environment:
Rhel 5x and 6x clients authenticated through NIS and windows 7 clients authenticated through Samba pdc. NIS and Samba both run on 6.5 RHEL server. Users migrate between places, using both, Linux and Windows clients, so all users are setup in Samba and in Linux. The solution is apparently implementation of LDAP to make user management simpler.

concerns:
- go with the 389-ds or with openldap
- if the 389, then which source for installation to use?

epel repository contains:
389-admin.i686 1.1.35-1.el6 epel
389-admin.x86_64 1.1.35-1.el6 epel
389-admin-console.noarch 1.1.8-1.el6 epel
389-admin-console-doc.noarch 1.1.8-1.el6 epel
389-adminutil.i686 1.1.19-1.el6 epel
389-adminutil.x86_64 1.1.19-1.el6 epel
389-adminutil-devel.i686 1.1.19-1.el6 epel
389-adminutil-devel.x86_64 1.1.19-1.el6 epel
389-console.noarch 1.1.7-1.el6 epel
389-ds.noarch 1.2.2-1.el6 epel
389-ds-console.noarch 1.2.6-1.el6 epel
389-ds-console-doc.noarch 1.2.6-1.el6 epel
389-dsgw.x86_64 1.1.11-1.el6 epel

while RHEL6 repo:
389-ds-base.x86_64 1.2.11.15-29.el6 rhel-dvd
389-ds-base-libs.i686 1.2.11.15-29.el6 rhel-dvd
389-ds-base-libs.x86_64 1.2.11.15-29.el6 rhel-dvd

  • so install only from epel or only from vendor repo - or is it possible to install base from vendor repo and add admin tools from epel?

Thank you for any comments

Responses