freeipa/install
Fraser Tweedale 3e33857827
Remove caJarSigningCert profile and related code
The caJarSigningCert profile was used for issuing the object signing
certificate for signing the Firefox auto-configuration extension
(XPI).  We removed the extension and object signing certificate some
time ago, so remove the profile and the related code that sets it
up.

Fixes: https://pagure.io/freeipa/issue/7226
Reviewed-By: Rob Crittenden <rcritten@redhat.com>
2017-11-01 12:39:19 +01:00
..
certmonger ipa-cacert-manage renew: switch from ext-signed CA to self-signed 2017-10-18 12:34:03 +02:00
conf Remove XPI and JAR MIME types from httpd config 2017-11-01 12:39:19 +01: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 Remove caJarSigningCert profile and related code 2017-11-01 12:39:19 +01:00
tools ipa-ca-install: mention REPLICA_FILE as optional in help 2017-10-30 10:49:13 +01:00
ui browser config: cleanup after removal of Firefox extension 2017-09-21 10:27:14 +02:00
updates ldap: limit the retro changelog to dns subtree 2017-10-26 12:40:28 +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

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.