freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

Files

Martin Kosek d27878ce9d Update mod_wsgi socket directory

Fedora 19 splitted /var/run and /run directories. Update mod_wsgi
configuration so that it generates its sockets in the right one.

2013-03-29 08:59:50 +01:00

certmonger

Remove unused krbV imports

2013-02-01 08:13:17 +01:00

conf

Update mod_wsgi socket directory

2013-03-29 08:59:50 +01:00

ffextension

Kerberos authentication extension makefiles

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

html

Move of Web UI non AMD dep. libs to libs subdirectory

2013-01-18 15:10:36 +01:00

migration

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

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

Pull translation files from Transifex

2012-10-11 16:09:27 -04:00

restart_scripts

Remove support for DN normalization from LDAPClient.

2013-03-01 16:59:47 +01:00

Put pid-file to named.conf

2013-03-29 08:59:45 +01:00

tools

Put pid-file to named.conf

2013-03-29 08:59:45 +01:00

Fixed Web UI build error caused by rhino changes in F19

2013-03-21 09:30:35 +01:00

updates

Configure ipa_dns DS plugin on install and upgrade

2013-03-22 14:31:22 +01:00

configure.ac

Updated makefiles to build FreeIPA Web UI layer

2013-01-18 15:10:37 +01:00

Makefile.am

Move CRL publish directory to IPA owned directory

2012-10-09 16:00:01 +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.