freeipa

0 Fork 0

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2026-10-13 00:42:03 -05:00

Files

T

Petr Viktorin b27267b00a Don't add another nsDS5ReplicaId on updates if one already exists

Modify update file to use default: rather than add: in
cn=replication,cn=etc,$SUFFIX.

Drop quotes around nsDS5ReplicaRoot because default: values
are not parsed as CSV.

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

2013-02-06 12:22:00 +01:00

certmonger

Remove unused krbV imports

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

conf

Enable mod_deflate

2013-01-17 17:19:29 +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 DN objects instead of strings

2012-08-12 16:23:24 -04:00

Pull translation files from Transifex

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

restart_scripts

Remove unused krbV imports

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

Update anonymous access ACI to protect secret attributes.

2013-01-23 15:31:48 -05:00

tools

Port ipa-replica-prepare to the admintool framework

2013-02-01 13:44:59 -05:00

Change tests to use AMD loader

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

updates

Don't add another nsDS5ReplicaId on updates if one already exists

2013-02-06 12:22:00 +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.