freeipa

0 Fork 0

Files

T

Petr Voborník fccea2dca4 Automember UI - default groups

In this patch was implemented and added a control for defining default automember groups.

There is a difference from UXD spec. In the spec the control was placed below table in the search facet. This was not working well with the combobox in the control. Open combobox requires some space below it. As it was placed at the bottom of the page it created unwanted blank space and forced showing scrollbars. Moving the control above the table solves the problem without rewriting combobox logic. It can be rewritten and moved down later.

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

2012-02-07 00:48:07 -06:00

conf

Configure s4u2proxy during installation.

2012-01-10 22:39:26 -05:00

html

Fixed inconsistent image names.

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

migration

ticket 2022 - modify codebase to utilize IPALogManager, obsoletes logging

2011-11-23 09:36:18 +01:00

update i18n pot file for branch master

2012-01-03 16:36:34 -05:00

Configure s4u2proxy during installation.

2012-01-10 22:39:26 -05:00

tools

Fix 'no-reverse' option description

2012-02-02 17:50:55 -05:00

Automember UI - default groups

2012-02-07 00:48:07 -06:00

updates

Use correct template variable for hosts, FQDN.

2012-01-17 17:51:12 +01:00

configure.ac

Fixed inconsistent image names.

2011-10-27 14:05:12 +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.