On 2.4.2019 12.11, Jan Tomasek wrote:
> Hi,
>
> I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
> replicas all on RedHat which I would like to abandon in favor Debian
> which is my main platform.
>
> My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
> co
Adding T attribute to the ca_cert solved the problem.
Thank you for your help.
Eli
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getf
Adding the T attribute to the ca_cert solved the problem.
Thank you for your help!
Eli
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https:/
> On 3 Apr 2019, at 04:39, Vandenburgh, Steve Y
> wrote:
>
> Believe that you may need the "T" trust setting on the CA certificate too:
>
> certutil
> -t trustargs
> Specify the trust attributes to modify in an existing certificate
> or to apply to a certificate when creat
> On 2 Apr 2019, at 23:46, Mark Reynolds wrote:
>
> Hi Jan,
>
> On 4/2/19 5:11 AM, Jan Tomasek wrote:
>> Hi,
>>
>> I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
>> replicas all on RedHat which I would like to abandon in favor Debian
>> which is my main platform.
>>
Believe that you may need the "T" trust setting on the CA certificate too:
certutil
-t trustargs
Specify the trust attributes to modify in an existing certificate
or to apply to a certificate when creating it or adding it to a
database. There are three available tr
Hello,
I am trying to setup a mutual based TLS authenticated 389-DS LDAP server, where
the client and the server will perform certificate based authentication.
This should be test system and not a production system.
I have a Windows CA signed on the LDAP server certificate and the client
certif
Hi Jan,
On 4/2/19 5:11 AM, Jan Tomasek wrote:
Hi,
I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
replicas all on RedHat which I would like to abandon in favor Debian
which is my main platform.
My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
complet
Hi,
I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
replicas all on RedHat which I would like to abandon in favor Debian
which is my main platform.
My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
completely missing 389-admin package [1]. They ship cock
