freeipa

0 Fork 0

Files

T

Martin Kosek f49c26db2c Switch httpd to use default CCACHE

Stock httpd no longer uses systemd EnvironmentFile option which is
making FreeIPA's KRB5CCNAME setting ineffective. This can lead in hard
to debug problems during subsequent ipa-server-install's where HTTP
may use a stale CCACHE in the default kernel keyring CCACHE.

Avoid forcing custom CCACHE and switch to system one, just make sure
that it is properly cleaned by kdestroy run as "apache" user during
FreeIPA server installation process.

https://fedorahosted.org/freeipa/ticket/4084

2014-01-22 10:14:05 +01:00

certmonger

Use /usr/bin/python2

2014-01-03 09:46:05 +01:00

conf

Use only system fonts

2014-01-21 12:05:09 +01:00

ffextension

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04:00

html

Load updated Web UI files after server upgrade

2013-10-16 18:06:30 +02:00

migration

Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py

2013-03-13 12:36:33 +01:00

Use /usr/bin/python2

2014-01-03 09:46:05 +01:00

restart_scripts

Revert restart scripts file permissions change

2014-01-08 09:54:53 +01:00

ipa-adtrust-install: configure host netbios name by default

2014-01-20 10:35:03 +01:00

tools

Switch httpd to use default CCACHE

2014-01-22 10:14:05 +01:00

Trust domains Web UI

2014-01-21 12:24:54 +01:00

updates

sudoOrder missing in sudoers

2014-01-15 11:00:35 +01:00

wsgi

Generate plugin index dynamically

2013-05-06 16:22:30 +02:00

configure.ac

RCUE initial commit

2014-01-21 12:04:02 +01:00

Makefile.am

Change group ownership of CRL publish directory

2013-07-16 12:17:40 +02: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.