freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-01-13 09:41:55 -06:00

History

Adam Young 07ace112af aci ui Implements the role, privilege, permission, delegation and selfservice entities ui. Targetgroup has been added to the object types. The groups lists need to be filter. The filter is currently hidden, with a hyperlink that reads 'filter' to unhide it. Each keystroke in this filter performs an AJAX request to the server. There are bugs on the server side that block some of the functionality from completing Creating a Permission requires one of 4 target types. The add dialog in this version assumes the user will want to create a filter type. They can change this on the edit page. Most search results come back with the values as arrays, but ACIs seem not to. Search and details both required special code to handle non-arrays. The unit tests now make use of the 'module' aspect of QUnit. This means that future unit test will also need to specify the module. The advantage is that multiple tests can share a common setup and teardown. Bugs that need to be fixed before this works 100% are https://fedorahosted.org/freeipa/ticket/634 https://fedorahosted.org/freeipa/ticket/633		2010-12-20 23:32:06 -05:00
..
conf	SUDO Rule Search and Details Pages	2010-11-19 16:53:30 -05:00
html	type prevented rendering on firefox4	2010-12-17 16:07:09 -05:00
migration	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
po	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
share	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
static	aci ui	2010-12-20 23:32:06 -05:00
tools	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
updates	Move automount, default HBAC services, netgroup and hostgroup bootstrapping.	2010-12-17 17:31:19 -05:00
configure.ac	build tweaks - use automake's foreign mode, avoid creating empty files to satisfy gnu mode - run autoreconf -f to ensure that everything matches	2010-11-29 11:39:55 -05: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.