IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-24 08:00:02 -06:00
Code Issues Packages Projects Releases Wiki Activity
1699cff350
freeipa/install
History
Fraser Tweedale 1699cff350 Remove duplicate references to external CA type 
Part of: https://pagure.io/freeipa/issue/6858

Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com>
2017-10-04 10:09:18 +02:00
..
certmonger Fix external renewal for CA with non-default subject DN 2017-09-01 11:46:49 +02:00
conf Changing cert-find to go through the proxy instead of using the port 8080 2017-06-16 08:56:53 +02:00
html browser config: cleanup after removal of Firefox extension 2017-09-21 10:27:14 +02:00
migration logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
oddjob wsgi, oddjob: remove needless uses of Env 2017-07-14 15:55:59 +02:00
restart_scripts Fix Certificate renewal (with ext ca) 2017-08-30 12:58:58 +02:00
share Move tmpfiles.d configuration handling back to spec file 2017-08-30 13:05:23 +02:00
tools Remove duplicate references to external CA type 2017-10-04 10:09:18 +02:00
ui browser config: cleanup after removal of Firefox extension 2017-09-21 10:27:14 +02:00
updates Adds whoami DS plugin in case that plugin is missing 2017-09-05 14:07:02 +02:00
wsgi logging: do not log into the root logger 2017-07-14 15:55:59 +02:00
Makefile.am Configure HTTPD to work via Gss-Proxy 2017-02-15 07:13:37 +01: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.