freeipa/install
Rob Crittenden 3fdca99c48 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
2011-07-17 22:16:32 -04:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html HBAC deny warning 2011-07-06 21:52:00 +00:00
migration Removed FreeWay font files. 2011-06-20 12:59:05 -04:00
po Make dogtag an optional (and default un-) installed component in a replica. 2011-06-23 19:04:33 -04:00
share Disallow direct modifications to enrolledBy. 2011-07-14 19:11:49 -04:00
tools Create tool to manage dogtag replication agreements 2011-07-17 22:16:32 -04:00
ui Fixed label capitalization 2011-07-14 11:44:48 -04:00
updates Disallow direct modifications to enrolledBy. 2011-07-14 19:11:49 -04:00
configure.ac rename static to ui 2011-01-20 14:12:47 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.