Rats. That's pretty much the conclusion I'd reached, but I'd hoped I
was wrong, based on the wiki page. Unfortunately, for account
terminations, we need more than just the ldif export/import, and
Security is kind of cranky about the lack.
Thanks for the answer. I guess I'll cross my fingers
Currently, OpenLDAP and 389 have totally different replication
mechanisms, so you can't really replicate between the two.
You can of course export / import filtered LDIF in either direction,
which, depending on the need, is occasionally good enough.
Anne Cross wrote:
I've been through the FDS/3
I've been through the FDS/389 website, and the best I've come up with is
this: http://directory.fedoraproject.org/wiki/Howto:OpenldapIntegration
Unfortunately, that gives me the sync in the wrong direction. We have
pre-existing OpenLDAP servers that belong to a different group. We're
suppose
Techie wrote:
On Thu, Jul 30, 2009 at 6:24 AM, Rich Megginson wrote:
Techie wrote:
Greetings all,
Is it possible to add the supportedExtension: 1.3.6.1.4.1.4203.1.11.1
to the 389 Directory server?
It's not there? It should already be listed:
ldapsearch -x -s base -b ""
dn:
...
On Thu, Jul 30, 2009 at 6:24 AM, Rich Megginson wrote:
> Techie wrote:
>>
>> Greetings all,
>> Is it possible to add the supportedExtension: 1.3.6.1.4.1.4203.1.11.1
>> to the 389 Directory server?
>>
>
> It's not there? It should already be listed:
> ldapsearch -x -s base -b ""
> dn:
> ...
> suppo
Hi all,
Does someone had problems upgrading a cluster with 2 multi-master servers
and several consumers?
We are planning a upgrade, first one master, than the other. Consumers will
be upgraded eventually.
Is the aproach correct?
Regards,
Daniel Cruz
--
389 users mailing list
389-us...@r
Techie wrote:
Greetings all,
Is it possible to add the supportedExtension: 1.3.6.1.4.1.4203.1.11.1
to the 389 Directory server?
It's not there? It should already be listed:
ldapsearch -x -s base -b ""
dn:
...
supportedExtension: 2.16.840.1.113730.3.5.9
supportedExtension: 2.16.840.1.113730.3
