freeipa

0 Fork 0

Files

T

Convert the tab lists to arrays of objects with four potential fields:

tab[0] -> tab.name
tab[1] -> tab.label
tab[2] -> tab.setup or tab.children

Added unit tests for nav_setup and nav_select_tab

2010-09-29 09:30:09 -04:00

conf

IPA HTTPD config uses /usr/share/static as target for /ipa/ui

2010-08-09 15:07:06 -04:00

html

Get merged tree into an installalble state.

2009-02-03 15:29:20 -05:00

migration

Add DS migration plugin and password migration page.

2010-01-20 16:54:17 -05:00

Fix the 'add' button

2010-09-28 10:20:30 -04:00

Add plugins for Sudo Commands, Command Groups and Rules

2010-09-27 22:38:06 -04:00

static

tab objects

2010-09-29 09:30:09 -04:00

tools

Remove spurious error in server uninstaller about client uninstall failure.

2010-09-24 15:31:44 -04:00

updates

Enabling SUDO support

2010-09-16 11:31:27 -04:00

configure.ac

Changes to the install and config files to support deploying the javascript code.

2010-08-06 11:55:52 -04:00

Makefile.am

Changes to the install and config files to support deploying the javascript code.

2010-08-06 11:55:52 -04: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.