freeipa

0 Fork 0

Files

T

Endi S. Dewata 620c085ebf Certificate management with self-signed CA

The certificate_status_widget has been modified to check for the
environment variable ra_plugin to determine the CA used by IPA
server. If self-signed CA is used, some operations will not be
available (e.g. checking certificate status, revoking/restoring
certificate), so the corresponding interface will be hidden. Other
operations such as creating new certificate and viewing certificate
are still available.

2010-12-02 11:54:58 -05:00

conf

SUDO Rule Search and Details Pages

2010-11-19 16:53:30 -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

Re-implement access control using an updated model.

2010-12-01 20:42:31 -05:00

static

Certificate management with self-signed CA

2010-12-02 11:54:58 -05:00

tools

Verify the --ip-address option when setting up DNS.

2010-11-24 09:18:57 -05:00

updates

Re-implement access control using an updated model.

2010-12-01 20:42:31 -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.