Hi,
I'm new to this list, so let me introduce myself. I'm a 52-year old
Austrian living in South France, and I'm the manager of a small IT
company with a focus on Linux and Open Source Software.
I'm the system administrator of our local school, where I have setup a
small 100 % GNU/Linux network
Le 19/08/2019 à 11:24, Marc Muehlfeld a écrit :
> If you are interested in single sign-on, automount, etc., FreeIPA (aka
> "Identity Management" in Red Hat) might be interesting for you.
FreeIPA is a bit dependency-heavy. I gave it a spin a few years back,
and it draws in a whole kitchen sink of
Le 20/08/2019 à 02:22, William Brown a écrit :
>
> Hello fellow Australian!
Austria, not Australia. No kangaroos here. :o)
>
> As for the setup - you may notice the Centos7 doesn't match the port389
> quickstart as those tools are part of 1.4.x. Today you can get those through:
>
> * Fedora
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-*
Le 20/08/2019 à 02:17, William Brown a écrit :
> We've changed from perl -> python between version 1.3.x and 1.4.x. If
> you are running RHEL7/Centos7/SLE-15/SUSE-leap-15 you will have the
> 1.3.x version with perl tools.
Maybe a little suggestion.
On the QuickStart page, add a clearly visible
Hi,
So it looks like my 389 DS server is running. I admit I'm fighting every
step to get this thing to run.
As it looks, the next step is to test the LDAP client connection. Which
leads me to my first question.
When TLS is enabled, is it still possible to get plain (e. g.
unencrypted)
icate for 389 DS under CentOS 7, which works.
--8<--
#!/bin/bash
#
# 389-ds-cert.sh
#
# Nicolas Kovacs, 2019
#
# Créer un certificat SSL auto-signé pour 389 Directory Server.
HOST=$(hostname -s)
FQDN=$(hostname --fqdn)
openssl
Hi,
Over the last couple of weeks, I've experimented quite a lot with 389
Directory Server. I've had good help on this list, so I wanted to thank
you guys.
I've started to write a series of blog articles about 389 DS, and I've
added two honorable mentions for Marc Muehlfeld and William Brown,
Hi,
I've just completed a detailed blog article series about central
authentication using 389 Directory Server. It's in French, and I
published it on my tech blog.
* https://www.microlinux.fr/389-ds-centos-7/
* https://www.microlinux.fr/389-ds-utilisateurs-centos-7/
*
Hi,
So I finally managed to get a 389 Directory Server up and running on a
spare CentOS 7 server. I can open the console even on a remote desktop
(using ssh -X), connect to my LDAP database, create a handful of users,
and I even managed to setup TLS.
The next step is getting a Linux client to
Le 23/08/2019 à 16:52, Marc Muehlfeld a écrit :
> Instead of using only a self-signed cert, wouldn't it make more sense to
> 1) create your own CA
> 2) create a CSR using certutil (see RHDS docs, section 9.3.2)
> 3) let your CA issue the cert
> 4) import the CA cert (see RHDS docs, section 9.3.3)
Le 04/09/2019 à 15:54, Mark Reynolds a écrit :
> Instead, we have a new web UI that is a Cockpit plugin (cockpit-389-ds)
> [1]. The new Cockpit UI is solely for administering and configuring the
> server. As previously announced there will not be an LDAP browser as
> part of the new UI. So
of "Standard branch for configuration information", I get
"Standardbranchforconfigurationinformation", "Secure connection" reads
"Secureconnection", etc.
I tried to add a user in my directory, with "Nicolas Kovacs" in the "Common
Name"
Hi,
After some more experimenting, I can confirm this is a serious bug. After
updating all packages on the system, it just reappeared.
Here's how you can reproduce it.
1. Install CentOS 7.7 but without updating the system.
2. Activate EPEL.
3. Install 389-ds.
3. Setup 389 DS.
4. Launch 389
Le 26/04/2020 à 15:46, Mark Reynolds a écrit :
> This is a bug in the java openJDK package (another reason our new UI is NOT in
> java):
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1791982
>
> It's supposed to be fixed in java-11-openjdk-11.0.7.1-0.1.ea.el7 according to
> the bug
>
> Try
15 matches
Mail list logo
