summaryrefslogtreecommitdiffstats
path: root/version.m4.in
diff options
context:
space:
mode:
authorRob Crittenden <rcritten@redhat.com>2011-07-14 23:35:01 -0400
committerRob Crittenden <rcritten@redhat.com>2011-07-17 22:16:32 -0400
commit3fdca99c48f19d6af7182b69bea0ee11100a9dd7 (patch)
tree4d50a038687198d36555ca531da415a125f2c25e /version.m4.in
parent2f650b60a4ce9c9b19a64b21ebe3051668efb4af (diff)
downloadfreeipa-3fdca99c48f19d6af7182b69bea0ee11100a9dd7.tar.gz
freeipa-3fdca99c48f19d6af7182b69bea0ee11100a9dd7.tar.xz
freeipa-3fdca99c48f19d6af7182b69bea0ee11100a9dd7.zip
Create tool to manage dogtag replication agreements
For the most part the existing replication code worked with the following exceptions: - Added more port options - It assumed that initial connections were done to an SSL port. Added ability to use startTLS - It assumed that the name of the agreement was the same on both sides. In dogtag one is marked as master and one as clone. A new option is added, master, the determines which side we're working on or None if it isn't a dogtag agreement. - Don't set the attribute exclude list on dogtag agreements - dogtag doesn't set a schedule by default (which is actually recommended by 389-ds). This causes problems when doing a force-sync though so if one is done we set a schedule to run all the time. Otherwise the temporary schedule can't be removed (LDAP operations error). https://fedorahosted.org/freeipa/ticket/1250
Diffstat (limited to 'version.m4.in')
0 files changed, 0 insertions, 0 deletions