freeipa

0 Fork 0

Files

T

Petr Vobornik bf7ee6eeec webui: facet policies for all facets

Now also facets other than details facet can use facet policies.

Facet policies purpose is to extend facets behavior without
overriding base class. This shared behavior could be reused in
several other facets which may have completely different
base classes.

Reviewed-By: David Kupka <dkupka@redhat.com>
Reviewed-By: Thierry Bordaz <tbordaz@redhat.com>

2015-05-20 14:04:10 +02:00

certmonger

Adopted kinit_keytab and kinit_password for kerberos auth

2015-04-20 08:27:35 +00:00

conf

2015-05-19 12:59:18 +00:00

ffextension

webui: append network.negotiate-auth.trusted-uris

2014-09-11 09:41:51 +02:00

html

webui: remove remnants of jquery-ui

2014-06-10 10:23:22 +02:00

migration

ipaplatform: Move all filesystem paths to ipaplatform.paths module

2014-06-16 19:48:20 +02:00

Add a KRA to IPA

2014-08-22 09:59:31 +02:00

restart_scripts

Adopted kinit_keytab and kinit_password for kerberos auth

2015-04-20 08:27:35 +00:00

DNSSEC: update OpenDNSSEC KASP configuration

2015-05-19 12:50:56 +00:00

tools

Pylint: fix false positive warning for domain

2015-05-19 19:14:58 +02:00

webui: facet policies for all facets

2015-05-20 14:04:10 +02:00

updates

Server Upgrade: Fix uniqueness plugins

2015-05-19 12:45:41 +00:00

wsgi

Remove trivial path constants from modules

2014-11-04 12:57:01 +01: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.