https://fedorapeople.org/groups/389ds/ci/nightly/2020/06/23/report-389-ds-base-1.4.4.3-20200622gitfe48b60.fc32.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.
https://pagure.io/389-ds-base/pull-request/51173
--
389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
h
> On 16 Jun 2020, at 09:37, Mark Reynolds wrote:
>
>
> On 6/11/20 8:15 PM, William Brown wrote:
>> Hi all,
>>
>> Background: https://pagure.io/389-ds-base/issue/51140
>>
>>
>> Ludwig and Mark both raised some good points here. First is that features
>> today (EntryUUID, LDAPSsoToken) are b
Hi all,
I've been a bit stuck on this problem, and I was hoping for some advice or
thoughts.
So, part of the migration from openldap, and in general, is that we support
entryuuid. That's all fine. I made a decision to allow entryuuid to diverge
from nsuniqueid, as entryuuid is often a primary
