freeipa

0 Fork 0

Files

T

Petr Vobornik 950a5da34d Validation of details facet before update https://fedorahosted.org/freeipa/ticket/1676 The ticket is a duplicate of server error, but it revealed few UI errors.

Newly performs validation of details facet before update. If validation fails, notification dialog is shown and command isn't executed.
Fixed integer minimum and maximum value checking.
Read-only and non-writable fields are no longer considered required.

2011-08-25 00:50:52 +00:00

conf

Add option to install without the automatic redirect to the Web UI.

2011-08-18 23:24:29 -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 1650 - compute accurate translation statistics

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

Change the way has_keytab is determined, also check for password.

2011-08-24 14:12:01 +02:00

tools

Suppress 389-ds debug output when starting services

2011-08-24 13:54:08 +02:00

Validation of details facet before update https://fedorahosted.org/freeipa/ticket/1676 The ticket is a duplicate of server error, but it revealed few UI errors.

2011-08-25 00:50:52 +00:00

updates

Change the way has_keytab is determined, also check for password.

2011-08-24 14:12:01 +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.