IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-30 10:47:08 -06:00
Code Issues Packages Projects Releases Wiki Activity
6802ea7d70
freeipa/install
History
Endi S. Dewata 6802ea7d70 Fixed problem changing page in association facet. 
The association facet has been modified to detect page change to
determine whether the facet needs to be updated.

Ticket #1459
2011-11-07 15:07:02 +01:00
..
conf Revert "Always require SSL in the Kerberos authorization block." 2011-09-27 08:54:42 +02:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
po Ticket 1718 - Fix Spanish po translation file 2011-10-11 22:46:02 -04:00
share Fix nis netgroup config entry so users appear in netgroup triple. 2011-10-27 09:55:58 +02:00
tools Fix ipa-replica-conncheck port labels 2011-11-04 08:55:25 +01:00
ui Fixed problem changing page in association facet. 2011-11-07 15:07:02 +01:00
updates Fix nis netgroup config entry so users appear in netgroup triple. 2011-10-27 09:55:58 +02:00
configure.ac Fixed inconsistent image names. 2011-10-27 14:05:12 +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.