> On 20 Aug 2019, at 18:42, Nicolas Kovacs <info@xxxxxxxxxxxxx> wrote: > > Hi, > > I spent some more time reading and experimenting. I'm slowly beginning > to see a path emerge in the directory jungle. Here's some odd notes, > impressions and questions. > > 1. Setting up a basic directory using 389 DS is extremely easy. It's > more or less just a matter of installing 389-ds-* related packages on > the server, run the 389-*.pl setup script, connect to the database and > then add user information. Doing the same thing using OpenLDAP is a > relatively painful experience, since it involves manually configuring > and setting up things using ldapmodify, ldapadd and a bunch of > handcrafted LDIF files. My basic instinct tells me to rather opt for 389 > DS for that reason. Thanks! I hope you will be just as impressed by our new python tools which I think are easier than the pl tools again! > > 2. I setup a complete 389 DS on a spare sandbox machine running CentOS 7 > in my office. Since the 389 Console requires a graphical environment, I > setup X11 and installed a basic window manager (WindowMaker, my first > one back in 2001 under Slackware 7.1). Worked like a charm even on my > very first attempt. I vaguely sense I like 389 DS. This graphical console is soon to be replaced by a web-based cockpit ui as part of CentOS8. So you may find it will go away in the future. > > 3. I did a Quick & Dirty setup on a sandbox client desktop running > OpenSUSE Leap 15.1 KDE. On the 389 DS server I created a few users and > filled in the relevant POSIX account information. On the clients I > opened YaST and pointed it to my 389 DS server instead of local > authentication. No NFS for the moment, I just created the corresponding > home directories manually for the moment. Logged out and found all my > users in the SDDM login manager. Tried to log in. JustWorks(tm). :o) Great! Happy to hear this! If you have any issues with the Yast modules for auth, I help maintain them, but I'm happy to hear they worked so easily. > > 4. Ideally, I would like to only install the minimal 389-ds-base package > on the server, and then use a lightweight tool to manage my directory > instead of the 389 Console that requires a graphical environment. As far > as I can tell, there's solutions like PHPLdapAdmin or LDAP Account > Manager for the server. Aren't there any simple GUI tools that I can > install on my laptop (MacBook Pro running OpenSUSE Leap 15.1 instead of > Mac OS) and that enable me to connect to my directory? I found some > tools like GQ or JXplorer, but they all seem unmaintained/dead. Any > suggestions? See above for the cockpit ui. Additionally in 389-ds 1.4.x we have a richer CLI suite that has much more depth and richness to what you can do. Really happy to hear you are impressed by 389-ds, and I hope we can continue to deliver a great experience! > > Cheers from the sunny South of France, > > Niki > -- > Microlinux - Solutions informatiques durables > 7, place de l'église - 30730 Montpezat > Site : https://www.microlinux.fr > Mail : info@xxxxxxxxxxxxx > Tél. : 04 66 63 10 32 > Mob. : 06 51 80 12 12 > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
