IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00
Code Issues Packages Projects Releases Wiki Activity
9dff149830
freeipa/install
History
Endi Sukma Dewata 9dff149830 Load user data and policies in a single batch. 
The user details facet has been modified to load the user data,
password policy and Kerberos ticket policy in a single batch
command.

Ticket #703
2012-01-10 18:44:35 +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 ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging 2011-11-23 09:36:18 +01:00
po update i18n pot file for branch master 2012-01-03 16:36:34 -05:00
share Add SELinux user mapping framework. 2011-12-09 16:46:25 +02:00
tools Add DNS check to conncheck port probe 2012-01-03 16:41:15 -05:00
ui Load user data and policies in a single batch. 2012-01-10 18:44:35 +01:00
updates Add SELinux user mapping framework. 2011-12-09 16:46:25 +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.