freeipa

0 Fork 0

Files

T

Nalin Dahyabhai 4d85fb18a2 drop the group.upg NIS map

The group.upg NIS map was an experiment in providing UPG groups
dynamically, and is not one of the maps that I'd ever expect a NIS
client to "know" to search.  We should probably just drop it.

2011-02-14 11:35:03 -05:00

conf

rename static to ui

2011-01-20 14:12:47 +00:00

html

error handling style

2011-01-25 16:47:09 -05:00

migration

Fix migration page

2011-02-11 13:28:22 -05:00

Removed 'name' from 'Sudo Command Group name'.

2011-01-24 13:33:00 -05:00

drop the group.upg NIS map

2011-02-14 11:35:03 -05:00

tools

Handle bad DM password in ipa-host-net-manage & ipa-copmat-manage.

2011-02-14 10:13:52 -05:00

Fixed add service dialog box.

2011-02-11 16:27:59 -05:00

updates

Add permission/privilege for updating IPA configuration.

2011-02-14 10:22:55 -05:00

configure.ac

rename static to ui

2011-01-20 14:12:47 +00: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.