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
70d7ec587a
freeipa/install
History
Sumit Bose 12f4584f57 ipa-adtrust-install: create fallback group with ldif file 
Currently the framework is used to add the group but we want to avoid
that users are added explicitly to the group by removing the
objectclasses groupofnames, ipausergroup and nestedgroup and we want to
use a name with spaces in it. Both it not easy possible with the
framework, a LDIF file is used instead to create the group.

Fixes https://fedorahosted.org/freeipa/ticket/3147
2012-10-09 10:22:16 +02:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
ffextension Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
html Removal of delegation-uris instruction from browser config 2012-10-04 18:35:47 -04:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Update the pot file (translation source) 2012-09-12 22:04:16 -04:00
restart_scripts Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
share ipa-adtrust-install: create fallback group with ldif file 2012-10-09 10:22:16 +02:00
tools Add SIDs for existing users and groups at the end of ipa-adtrust-install 2012-10-04 22:15:36 -04:00
ui support multi-line error messages in exceptions 2012-10-09 10:18:40 +02:00
updates Add new ipaIDobject to DNA plugin configuraton 2012-10-04 22:15:36 -04:00
configure.ac Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04:00
Makefile.am Kerberos authentication extension makefiles 2012-10-04 18:07:34 -04: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.