freeipa.git/install/tools, branch network-fixes

Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place.

2011-08-09T11:12:19+00:00

ticket 1522

Re-arrange CA configuration code to reduce the number of restarts.

2011-08-04T00:38:07+00:00

Ade Lee from the dogtag team looked at the configuration code and
determined that a number of restarts were not needed and recommended
re-arranging other code to reduce the number of restarts to one.

https://fedorahosted.org/freeipa/ticket/1555

Improve error message in ipactl

2011-08-04T06:18:18+00:00

If a hostname configured in /etc/ipa/default.conf is changed and
is different from the one stored in LDAP in cn=ipa,cn=etc,$SUFFIX
ipactl gives an unintelligible error.

This patch improves the error message and also offers a list of
configured master so that the hostname setting in IPA configuration
can be easily fixed.

https://fedorahosted.org/freeipa/ticket/1558

Clean up existing DN object usage

2011-07-29T11:13:55+00:00

Fix external CA install.

2011-07-27T02:30:21+00:00

ticket 1523

Fix man page ipa-csreplica-manage

2011-07-25T08:55:33+00:00

Fix references to ipa-replica-manage in ipa-csreplica-manage.

https://fedorahosted.org/freeipa/ticket/1519

Fix ipa-compat-manage not working after recent ipa-nis-manage change.

2011-07-22T08:38:49+00:00

ticket 1147

Don't delete NIS netgroup compat suffix on 'ipa-nis-manage disable'.

2011-07-19T11:45:01+00:00

ticket 1469

Clean up of IP address checks in install scripts.

2011-07-19T10:30:47+00:00

Fixes ipa-dns-install incorrect warning.

ticket 1486

Create tool to manage dogtag replication agreements

2011-07-18T02:16:32+00:00

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