freeipa

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

Files

Martin Kosek 1816643a43 Update schema for bind-dyndb-ldap

Add new attributes and objectclasses to support new features:
  - global bind-dyndb-ldap settings in LDAP
  - conditional per-zone forwarding
  - per-zone configuration of automatic PTR updates
  - AllowQuery and AllowTransfer ACIs

https://fedorahosted.org/freeipa/ticket/2215
https://fedorahosted.org/freeipa/ticket/2072

2012-02-24 09:40:36 +01:00

conf

add session manager and cache krb auth

2012-02-09 13:20:45 -06:00

html

Fixed inconsistent image names.

2011-10-27 14:05:12 +00:00

migration

ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging

2011-11-23 09:36:18 +01:00

update translation pot file

2012-02-21 17:19:20 -05:00

Update schema for bind-dyndb-ldap

2012-02-24 09:40:36 +01:00

tools

Ease zonemgr restrictions

2012-02-20 15:34:45 +01:00

Added missing configuration options

2012-02-20 15:47:39 -06:00

updates

Update schema for bind-dyndb-ldap

2012-02-24 09:40:36 +01:00

configure.ac

Fixed inconsistent image names.

2011-10-27 14:05:12 +00:00

Makefile.am

rename static to ui

2011-01-20 14:12:47 +00: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.