IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity
a70b08e9ae
freeipa/install
History
Ana Krivokapic a70b08e9ae Do not crash if DS is down during server uninstall 
DS is contacted during server uninstallation, in order to obtain information
about replication agreements. If DS is unavailable, warn and continue with
uninstallation.

https://fedorahosted.org/freeipa/ticket/3867
2013-09-09 17:24:04 +02:00
..
certmonger Remove unused krbV imports 2013-02-01 08:13:17 +01:00
conf Do not redirect to https in /ipa/ui on non-HTML files 2013-06-26 15:02:13 +02:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Make ssbrowser.html work in IE 10 2013-06-04 12:24:13 +02:00
migration Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py 2013-03-13 12:36:33 +01:00
po Remove systemd upgrader as it is not used anymore 2013-08-15 08:49:15 +02:00
restart_scripts Make CS.cfg edits with CA instance stopped 2013-08-26 16:21:36 +02:00
share Add timestamps to named debug logs in /var/named/data/named.run 2013-09-06 15:39:36 +02:00
tools Do not crash if DS is down during server uninstall 2013-09-09 17:24:04 +02:00
ui Update idrange search facet after trust creation 2013-08-28 14:23:42 +02:00
updates Increase default SASL buffer size 2013-08-07 14:13:56 +02:00
wsgi Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
configure.ac Prevent *.pyo and *.pyc multilib problems 2013-08-13 15:31:46 +02: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.