freeipa/install
Endi S. Dewata c854435a27 HBAC Access Time
IPA commands now can be defined in these classes:
 - ipa_command: a single IPA command
 - ipa_batch_command: a batch command for executing multiple commands
   on the server side using the new batch plugin

The dialog boxes for adding and removing entries have been refactored:
 - ipa_dialog: base class for dialog boxes
 - ipa_adder_dialog: generic adder dialog box
 - ipa_deleter_dialog: generic deleter dialog box
 - ipa_association_adder_dialog: adding entity association
 - ipa_association_deleter_dialog: removing entity association

Dialog boxes for adding/deleting HBAC users, hosts, services, and
sourcehosts are implemented using the association dialog boxes.

The dialog box for adding access time is implemented using ipa_dialog
and currently contains only a text field. This will be replaced with a
custom dialog box in a separate patch.

The dialog box for removing access time is implemented using the
generic deleter class because it's not an association. Removing multiple
access times is implemented using batch operations.

New test data files for access times have been added.
2010-11-08 20:06:49 -05:00
..
conf Ticket Expiration 2010-11-08 14:17:47 -05: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
po Update Ukrainian (uk.po) translation 2010-10-19 14:14:23 -04:00
share add support for hostCategory and userCategory 2010-11-04 14:43:03 -04:00
static HBAC Access Time 2010-11-08 20:06:49 -05:00
tools Remove ipa-fix-CVE-2008-3274, it isn't needed any more. 2010-11-08 14:23:27 -05:00
updates Add additional default HBAC login services 2010-11-08 14:23:03 -05:00
configure.ac HBAC Details Page 2010-11-04 14:22:32 -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

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.