freeipa

0 Fork 0

Files

T

Making all of the page elements based on the font size.
Also, set the font to the defauklt for the browser.
By default, most brosers have Font set to 16px.

2010-11-16 11:19:34 -05:00

conf

Remove some more mod_python references

2010-11-10 17:38:17 -05:00

html

Get merged tree into an installalble state.

2009-02-03 15:29:20 -05:00

migration

Rewrite the migration page using WSGI

2010-11-09 13:25:17 -05:00

Fix test.po errors in make test

2010-11-15 11:46:42 -05:00

Increase # of chars in users and groups to 255 and default username to 32.

2010-11-12 17:25:40 -05:00

static

px to em

2010-11-16 11:19:34 -05:00

tools

Use a different user for dogtag DS instance

2010-11-12 17:26:43 -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

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.