freeipa

0 Fork 0

Files

T

Endi S. Dewata ebb0b386a3 Fixed problem with combobox.

The entity select widget has been modified to handle timing issue
in both dialog box and details page.

Ticket #1736

2011-08-31 16:29:55 +00:00

conf

enable proxy for dogtag

2011-08-29 17:54:49 -04:00

html

Fixed browser configuration pages

2011-08-17 17:28:25 +00:00

migration

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

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

ticket 1669 - improve i18n docstring extraction

2011-08-24 23:13:16 -04:00

Let Bind track data changes

2011-08-31 16:46:12 +02:00

tools

Let Bind track data changes

2011-08-31 16:46:12 +02:00

Fixed problem with combobox.

2011-08-31 16:29:55 +00:00

updates

Add additional pam ftp services to HBAC, and a ftp HBAC service group

2011-08-24 15:21:41 -04:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +02:00

Makefile.am

…

README.schema

…

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.