freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00

History

Martin Kosek 5a9a9723de IPA replica/server install does not check for a client When IPA replica or server is configured it does not check for possibly installed client. This will cause the installation to fail in the very end. This patch adds a check for already configured client and suggests removing it before server/replica installation. https://fedorahosted.org/freeipa/ticket/1002		2011-03-03 10:20:39 -05:00
..
conf	rename static to ui	2011-01-20 14:12:47 +00:00
html	error handling style	2011-01-25 16:47:09 -05:00
migration	Fix migration page	2011-02-11 13:28:22 -05:00
po	Final i18n unit test fixes.	2011-03-01 10:31:43 -05:00
share	Store list of non-master replicas in DIT and provide way to list them	2011-03-02 09:46:46 -05:00
tools	IPA replica/server install does not check for a client	2011-03-03 10:20:39 -05:00
ui	Use modified entity find commands for associations	2011-03-02 19:11:28 -05:00
updates	Store list of non-master replicas in DIT and provide way to list them	2011-03-02 09:46:46 -05: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

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.