freeipa

0 Fork 0

Files

T

Endi S. Dewata 566fa8ddc5 Fixed problem opening host adder dialog.

The hidden fqdn field in the host adder dialog has been changed to
use a generic widget instead of text widget to avoid null pointer
error since the UI elements are never created.

Ticket #1788

2011-09-14 23:58:49 +00:00

conf

Improved handling for ipa-pki-proxy.conf

2011-09-13 16:09:15 +02: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

Add ipa-adtrust-install utility

2011-09-14 18:45:13 -04:00

Add ipa-adtrust-install utility

2011-09-14 18:45:13 -04:00

tools

Add ipa-adtrust-install utility

2011-09-14 18:45:13 -04:00

Fixed problem opening host adder dialog.

2011-09-14 23:58:49 +00:00

updates

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

2011-09-13 17:36:59 +02:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +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.