freeipa

0 Fork 0

Files

T

Martin Basti 52b7101c11 Fix uniqueness plugins

* add uniqueness-subtree-entries-oc:posixAccount to ensure idviews users
will not be forced to have unique uid

* remove unneded update plugins -> update was moved to .update file

* add uniqueness-across-all-subtrees required by user lifecycle
management

Reviewed-By: Alexander Bokovoy <abokovoy@redhat.com>

2015-03-05 12:43:35 +01:00

certmonger

Make certificate renewal process synchronized

2015-01-13 18:34:59 +00:00

conf

Fixed KRA backend.

2014-11-04 16:33:16 +01:00

ffextension

webui: append network.negotiate-auth.trusted-uris

2014-09-11 09:41:51 +02:00

html

webui: remove remnants of jquery-ui

2014-06-10 10:23:22 +02:00

migration

ipaplatform: Move all filesystem paths to ipaplatform.paths module

2014-06-16 19:48:20 +02:00

Add a KRA to IPA

2014-08-22 09:59:31 +02:00

restart_scripts

Make certificate renewal process synchronized

2015-01-13 18:34:59 +00:00

Fix uniqueness plugins

2015-03-05 12:43:35 +01:00

tools

replica-install: Use different API instance for the remote server

2015-03-05 11:01:36 +01:00

webui: service: add ipakrbrequirespreauth checkbox

2015-02-26 00:26:22 +01:00

updates

Fix uniqueness plugins

2015-03-05 12:43:35 +01:00

wsgi

Remove trivial path constants from modules

2014-11-04 12:57:01 +01:00

configure.ac

RCUE initial commit

2014-01-21 12:04:02 +01:00

Makefile.am

Change group ownership of CRL publish directory

2013-07-16 12:17:40 +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.