freeipa

0 Fork 0

Files

T

This patch implements action panel. Action panel is a box located in facet details section which contains actions related to that object/section.

In spec file can be configured actions and title used in action panel. Default title is 'Actions'. Actions are specified by their name. They have to be defined in action collection in facet.

https://fedorahosted.org/freeipa/ticket/2248

2012-06-04 10:45:07 +02:00

conf

Implement password based session login

2012-02-27 05:57:43 -05:00

html

Fixed inconsistent image names.

2011-10-27 14:05:12 +00:00

migration

Forms based authentication UI

2012-03-02 11:04:33 +01:00

validate i18n strings when running "make lint"

2012-04-26 13:53:37 +02:00

restart_scripts

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -04:00

permission-find missed some results with --pkey-only option

2012-06-01 07:51:59 +02:00

tools

Move install script error handling to a common function

2012-05-31 14:37:27 +02:00

Action panel

2012-06-04 10:45:07 +02:00

updates

permission-find missed some results with --pkey-only option

2012-06-01 07:51:59 +02:00

configure.ac

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -04:00

Makefile.am

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -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.