freeipa

0 Fork 0

Files

T

Rob Crittenden 2ca7bb3134 Fix CS replication management.

The master side should be on the local side, replica1, not the
remote. This required reversing a few master variables. This impacts
the naming of the replication agreements.

When deleting an agreement pass in the DN of that agreement
rather than trying to calculate what it is on-the-fly. We cannot
be sure which side is the master/clone and since we search for it
anyway to determine if the agreement exists it is more correct
to use what we find.

The force flag wasn't being passed into del_link so there was no way
to force a deletion.

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

2012-10-09 15:45:44 -04:00

certmonger

Use DN objects instead of strings

2012-08-12 16:23:24 -04:00

conf

Move CRL publish directory to IPA owned directory

2012-10-09 16:00:01 +02:00

ffextension

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04:00

html

Removal of delegation-uris instruction from browser config

2012-10-04 18:35:47 -04:00

migration

Use DN objects instead of strings

2012-08-12 16:23:24 -04:00

Update the pot file (translation source)

2012-09-12 22:04:16 -04:00

restart_scripts

Use Dogtag 10 only when it is available

2012-09-17 18:43:59 -04:00

Minor fixes for default SMB group

2012-10-09 12:15:07 +02:00

tools

Fix CS replication management.

2012-10-09 15:45:44 -04:00

support multi-line error messages in exceptions

2012-10-09 10:18:40 +02:00

updates

Add uniqueness plugin configuration for sudorule cn

2012-10-08 18:32:41 -04:00

configure.ac

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04:00

Makefile.am

Move CRL publish directory to IPA owned directory

2012-10-09 16:00:01 +02:00

README.schema

Add some basic rules for adding new schema

2010-08-27 13:40:37 -04:00

README.schema

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.