freeipa

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

Files

Rob Crittenden 9dfb0f05b0 Use TLS for dogtag replication agreements.

Configure the dogtag 389-ds instance with SSL so we can enable TLS
for the dogtag replication agreements. The NSS database we use is a
symbolic link to the IPA 389-ds instance.

ticket 1060

2011-03-10 09:57:36 -05:00

conf

rename static to ui

2011-01-20 14:12:47 +00:00

html

error handling style

2011-01-25 16:47:09 -05:00

migration

Use ldapi: instead of unsecured ldap: in ipa core tools.

2011-03-03 14:04:34 -05:00

Final i18n unit test fixes.

2011-03-01 10:31:43 -05:00

Store list of non-master replicas in DIT and provide way to list them

2011-03-02 09:46:46 -05:00

tools

Use TLS for dogtag replication agreements.

2011-03-10 09:57:36 -05:00

Fixed self service page.

2011-03-08 17:05:01 -05:00

updates

Store list of non-master replicas in DIT and provide way to list them

2011-03-02 09:46:46 -05:00

configure.ac

rename static to ui

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