freeipa

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

Files

Endi S. Dewata df16d4aff7 Fixed duplicate entries in enrollment dialog.

The IPA.association_adder_dialog has been modified not to show
search results that are already selected to prevent duplicates.

Ticket #1859

2011-09-27 14:44:33 +00:00

conf

Revert "Always require SSL in the Kerberos authorization block."

2011-09-27 08:56:50 +02:00

html

Fixed browser configuration pages

2011-08-17 18:04:23 +00:00

migration

Fixed broken links in ipa_error.css and ipa_migration.css.

2011-08-11 13:38:36 +00:00

25 Create Tool for Enabling/Disabling Managed Entry Plugins

2011-09-21 09:23:02 +02:00

The precendence on the modrdn plugin was set in the wrong location.

2011-09-13 17:37:18 +02:00

tools

Revert "Always require SSL in the Kerberos authorization block."

2011-09-27 08:56:50 +02:00

Fixed duplicate entries in enrollment dialog.

2011-09-27 14:44:33 +00:00

updates

The precendence on the modrdn plugin was set in the wrong location.

2011-09-13 17:37:18 +02:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:26:10 +02: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.